Skip to main content
Glama

Retry failed people (spends credits)

retry_outreach

SPENDS CREDITS: quote_outreach_retry first, show the price, after the user's yes pass its credits as confirm_credits. [REST: POST /api/tasks/{id}/outreach/retry]

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>",
      "confirm_credits": "<confirm_credits>"
    },
    "name": "retry_outreach"
  }
}

Input Schema

NameRequiredDescriptionDefault
cidsNoThe failed people to retry; omitted: every failed person of the generation.
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

A3.8/5.0
Behavior3/5

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

Annotations already state this is a non-read-only, non-destructive, non-idempotent mutation, but they say nothing about cost; the description adds the critical fact that the call spends credits and requires explicit user confirmation via a quote. That is meaningful context beyond the structured fields. It stops short of disclosing the outcome of a retry (whether partial cid failures are possible, whether failed retries still consume credits), which matters for a paid mutation.

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?

A single front-loaded line leads with the most important fact (spends credits), then the required sequence in order, with a compact REST endpoint tag at the end. Nothing is padded.

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?

Given four parameters, full schema coverage, no output schema, and annotations covering the safety profile, the description supplies the one thing structured data lacks: the mandatory quote-then-confirm workflow. Minor gap: no indication of what a successful retry returns or how partial failures surface.

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 coverage is 100%, so all four parameters including confirm_credits and the optional cids/generation_id fallbacks are already documented in the schema. The description reinforces the confirm_credits-to-quote relationship but largely restates what the schema already says. Baseline 3 is appropriate.

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 description names the prerequisite tool quote_outreach_retry and encodes the whole credit workflow, which makes clear this is the confirming/spending step of retrying failed outreach. It doesn't state the retry action itself in a plain verb+resource sentence (that job is left to the name and title), but combined with the title an agent can identify the operation and distinguish it from quote_outreach_retry and start_outreach.

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

Usage Guidelines4/5

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

It gives an explicit ordering rule: call quote_outreach_retry first, show the price to the user, and only after a user 'yes' pass the quote's credits as confirm_credits. That is a real gating condition rather than vague context. It does not cover when to prefer this over other outreach entry points (e.g., start_outreach) or what to do if the quote is stale.

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