Let your agent guide your first Introduction

Give Codex, Claude or another agent a reliable reference and bounded tasks for preparing, checking and understanding your first mission.

Before you begin#

An agent that can read a guide; a Kite account connection is optional. Keep your objective in plain language.

Follow the steps#

1. Give the agent the University reference. Ask it to retrieve the relevant guide and version. The University provides JSON, Markdown and read-only search/get tools at https://kitegtm.com/university/api/mcp. It is educational knowledge, separate from the private connection at https://api.kitegtm.com/mcp.
2. State the objective and the allowed task. “Prepare a mission brief from these facts” and “Read this mission’s status” are concrete tasks. Supply only the business context needed and explain any information it must leave private.
3. Discover the connected Kite tools separately. Account access depends on a real connected app and its permissions. Tool names may have provider prefixes. Inspect the current tool catalogue and schema instead of assuming an example is installed.
4. Use read tools in order. list_missions returns mission IDs; use its returned market_id with get_mission. list_opportunities returns each row’s Introduction state. get_recent_activity and get_credit_balance answer their own bounded questions. A field not returned is unknown.
5. Use a recommendation when it helps. list_mission_recommendations returns recommendation IDs; get_mission_recommendation reads the proposed audience, roles, place and criteria for one. Review the strategy against your objective before requesting preparation. prepare_mission_recommendation saves a reviewable setup and starts nothing. The recipe below explains the handoff.
6. Review the output and finish in Kite. Ask for evidence, unknowns, the exact next in-app step and any returned review link. Never treat an agent’s confident wording as a success receipt.

Enlarge image

Read mission progress

Open full-size image Open full-size image

What you should see#

A useful agent report names the guide version, the connected tool and record used when applicable, what is supported, what remains unknown and what you should do next. A business strategy or buyer fit is not evidence that someone wants to talk. Report an Introduction from the opportunity's returned Introduction state and qualification evidence.

Review a recommended mission#

Use this task when you want help choosing a direction:

Read the current University guidance, then use my connected Kite tools to list mission recommendations and read the one that best supports my objective. Show its audience, place, roles, required criteria, reasoning and unknowns. Compare it with any relevant mission I already have. Recommend a next step without saving, refreshing, dismissing or starting anything.

The agent calls list_mission_recommendations, then get_mission_recommendation with the returned recommendation_id. It can use list_missions and a returned market_id with get_mission when needed to compare existing work. Each list is bounded; an incomplete page cannot establish that no other missions exist. A recommendation describes a strategy, not a confirmed interested person or an achieved result.

When you select a recommendation and ask the agent to prepare it, it calls prepare_mission_recommendation with that returned ID. The result supplies a review_url. Open that exact link to review the setup, complete any missing run settings and use Kite's Start control. The agent should report prepared only after a successful result. It should not say the mission is running, that people were contacted or that an Introduction was created. Asking to prepare the same recommendation again returns the existing setup.

If the result says an existing setup has already started, report that recorded state and use its returned mission ID to inspect progress when requested. Preparation did not start it again. An empty list, needs_refresh, an unavailable tool or a denied call is a useful stopping point. The agent should explain the returned state and the next step. Refreshing recommendations changes the saved list; dismissing one removes that audience from future recommendations. Neither belongs in a read-only comparison task.

Read progress and prepare a reply#

For progress, ask the agent to find one mission with list_missions, read it with get_mission and inspect relevant activity or opportunities. list_opportunities includes each row's introduction.state. Qualified or developing opportunities do not automatically count as Introductions. Credit balance and people-contacted figures answer different questions from monthly Reach. Keep missing fields unknown and preserve pagination when describing totals.

For a reply, first read the thread using an ID from list_conversations. Ask the agent to show the exact proposed wording. If you request a saved draft, reply_to_conversation saves it and returns a review link. Open that link to review and press Send in Kite. A draft result does not mean a reply was sent.

Campaign creation, settings, launch, enrollment and billing remain in the web app. If a result says needs_person, return its review link. For a queued contact import or removal, use get_contact_import or get_contact_job when available before reporting completion. Do not turn waiting, queued or partial results into success.

If something is missing#

If the connector is unavailable, the agent can still prepare a brief from supplied facts or explain a screenshot. It should say that account state is unverified. If a tool says needs_person, waiting, queued or draft, preserve that meaning and direct you to the product. Do not paste a token, password, OTP or private customer transcript into public University feedback.

Work with your agent#

Use the task below to prepare a useful next step. Give your agent current University guidance and only the business information it needs. Ask it to separate facts, assumptions and decisions that need your answer. If its tools cannot read something, the answer is unknown.

Read Kite University guidance for signup to first Introduction. Help me prepare or inspect one specific stage. First report which University and Kite account tools you actually have. Retrieve the relevant guide and cite its version. If account access is available, use only the read tools needed and IDs returned by those tools. Return supported facts, unknowns and the exact next step in Kite. Keep public guidance separate from my private account information.

Prepare guidance only. Do not change settings, create or start work, connect accounts, send messages, enroll contacts or spend money. Use current tool discovery; never invent capabilities or record IDs. Show missing evidence and the next step for me to review in Kite.

Check your next step#

The agent has the current University reference. Complete the readiness notes below, then use your Kite workspace to confirm what is actually saved. Checking a box here does not change your account.