Skip to main content
Glama

One person's messages

get_outreach_lead
Read-onlyIdempotent

One person of the outreach: the messages by step (network, kind, text, character limit, hook and the fact it uses, the post of a comment), the route and why, the findings of the research with sources, contacts. step_id, result_id and the revision are what the edit, rewrite and variant tools need. [REST: GET /api/tasks/{id}/outreach/leads/{cid}]

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>",
      "cid": "<cid>"
    },
    "name": "get_outreach_lead"
  }
}

Input Schema

NameRequiredDescriptionDefault
cidYesThe person's id (cid) from list_leads.
task_idYesThe search id (task id), e.g. from list_searches or create_search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds real value by disclosing the payload contents (per-step messages, route reasoning, research findings with sources, contacts) in the absence of an output schema. It does not mention pagination, size limits, or behavior when the lead has no outreach yet.

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

Conciseness3/5

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

The core content is packed into one dense, comma-spliced sentence with no verb, which slows comprehension. The bracketed REST endpoint note is mildly useful for debugging but is trailing metadata rather than guidance, and the payload enumeration could be structured as a short list.

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?

With no output schema, the description carries the burden of describing return contents, and it does so fairly thoroughly: per-step messages with their fields, routing rationale, research findings with sources, contacts, plus the ids downstream tools consume. What is missing is the shape of the response (flat vs nested, single vs list) and edge-case behavior.

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%, and both parameters already document their provenance (cid from list_leads, task_id from list_searches or create_search). The description adds no meaning beyond that; the ids it names (step_id, result_id, revision) are return values, not inputs.

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 enumerates what a single lead record contains (messages by step with network/kind/text/character limit/hook/fact, route and rationale, research findings with sources, contacts), which goes well beyond the title. It lacks an explicit verb ('returns'/'fetches') and does not state how it differs from the sibling get_lead or get_outreach, so it falls short of a 5.

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

Usage Guidelines3/5

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

It implies a workflow by noting that step_id, result_id and the revision are what the edit, rewrite and variant tools need, so an agent can infer 'call this before editing a message'. There is no explicit when-to-use statement and no exclusion telling the agent when to prefer get_lead or get_outreach instead.

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