Skip to main content
Glama

Write the messages (spends credits)

start_outreach

SPENDS CREDITS: quote_outreach first, show the price to the user and after their yes pass its credits as confirm_credits. Needs the sender ready, the essence and the accounts. Runs in the background (minutes); poll get_outreach every 30-60 s. [REST: POST /api/tasks/{id}/outreach/start]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "task_id": "<task_id>",
      "cids": "<cids>",
      "confirm_credits": "<confirm_credits>"
    },
    "name": "start_outreach"
  }
}

Input Schema

NameRequiredDescriptionDefault
cidsYesFit people (cid) of the search; get_outreach lists them.
task_idYesThe search id (task id), e.g. from list_searches or create_search.
generation_idNoThe outreach generation id (get_outreach campaign.generation.id); omitted: the current one.
confirm_creditsYesThe price in credits the matching quote returned, shown to the user and confirmed by them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint=false and idempotentHint=false, and the description adds real context beyond them: the call spends credits, the amount must be pre-confirmed by the user, and the job runs asynchronously for minutes requiring polling. It stops short of warning that a retry or duplicate call may spend credits again, which is the main residual risk given idempotentHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The cost warning is front-loaded in capitals, followed by the prerequisite sequence, then async behavior, then the endpoint. Every clause carries operational information; nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a non-idempotent, credit-spending background job with no output schema, the description covers cost confirmation, prerequisites, runtime duration, and the polling alternative. The only gap is failure handling — what state the task is left in if the call fails or credits run out mid-job.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all four parameters (including the generation_id default of 'the current one') are already documented in the schema. The description reinforces confirm_credits as the quote-derived price and loosely maps cids to 'the accounts', but adds no new syntax or value constraints beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The title plus 'SPENDS CREDITS' framing and the REST endpoint (POST /api/tasks/{id}/outreach/start) make clear this launches the outreach/message-writing job. It is clearly distinct from siblings quote_outreach and get_outreach, which it names as the quoting step and the polling step respectively. However, the description body never states in plain words that it writes/sends the messages or what object it operates on, leaning on the title to carry that.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It spells out the required ordering: call quote_outreach first, show the user the price, get their yes, then pass that quote's `credits` as confirm_credits. It also names prerequisites (sender ready, essence and accounts) and gives the operational follow-up (poll get_outreach every 30-60 s), so an agent knows both when to call it and what to do before and after.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources