Skip to main content
Glama

Outreach desk

get_outreach
Read-onlyIdempotent

The outreach («Рассылка») of a finished search: the campaign (sender with its card, essence = offer / ask / tone / rules / language, the accounts, counts, the current generation, credits charged) and the fit people with their state (paginated), plus what to do next (next). [REST: GET /api/tasks/{id}/outreach]

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
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 readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuine value beyond them: results are paginated, the payload includes credit charges and the current generation, and a `next` field indicates the follow-up action. It does not state ordering, page-size behavior, or error cases for a non-existent/incomplete search.

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?

Front-loaded with the resource and packed into one sentence, but the deeply nested parentheticals (sender with its card, essence = offer/ask/tone/rules/language) make it dense and harder to scan. The REST endpoint tag is useful; the rest earns its place but could be itemized.

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?

There is no output schema, so the description correctly takes on the job of describing what comes back — campaign details, lead states, and the `next` pointer — which is exactly what an agent needs before calling. Remaining gaps are minor: pagination completeness and behavior when the search has no outreach yet.

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 only 33% — task_id is documented in the schema, while limit and offset are left to their defaults/bounds. The description partially compensates by noting the result is paginated, and it references originating the task id from list_searches or create_search via the schema. No additional detail on pagination semantics (total counts, page exhaustion) is given.

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?

States a specific verb and resource: fetching the outreach/«Рассылка» belonging to a finished search, and enumerates the returned shape (campaign, sender, essence, accounts, counts, generation, credits, fit people with state, `next`). The 'of a finished search' scoping distinguishes it from sibling tools like get_outreach_lead or export_outreach, though it never names an alternative explicitly.

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?

Usage is implied by the phrase 'of a finished search' — i.e., use it once a search has completed and has an outreach campaign — and the mention of `next` hints at a workflow step. However, there is no explicit when-to-use/when-not guidance and no routing to get_outreach_lead, get_search_funnel, or export_outreach for adjacent needs.

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