Skip to main content
Glama

Read outreach

get_outreach
Read-onlyIdempotent

Outreach to people at companies (needs an Applystead membership): threads, people worth reaching with a drafted first email, suggestions, one message and the exact message a send would deliver, and Mailbox campaigns (one email each to the recruiter or hiring manager of many jobs) with their expected response, research, emails and approval. Actions: threads, cold_context, suggestions, get, preview, campaigns, campaign, campaign_targets, campaign_approval. Call with action "help" for each action's fields.

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

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNoFields for the action. Call with action "help" to list each action's fields.
campaign_idNoA campaign's id from get_outreach campaigns (campaigns[].id).
outreach_idNoAn outreach message or thread id from get_outreach.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "threads",
      -  "cold_context",
      -  "suggestions",
      -  "get",
      -  "preview",
      -  "help"
      -]New value: +[
      +  "threads",
      +  "cold_context",
      +  "suggestions",
      +  "get",
      +  "preview",
      +  "campaigns",
      +  "campaign",
      +  "campaign_targets",
      +  "campaign_approval",
      +  "help"
      +]
    • addedInput schema / properties / campaign_id
      Added value: +{
      +  "description": "A campaign's id from get_outreach campaigns (campaigns[].id).",
      +  "pattern": "^[a-f0-9]{32}$",
      +  "type": "string"
      +}
  2. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the description earns credit for the extra context it adds: the membership gate and, notably, that 'preview' shows 'the exact message a send would deliver' without sending, and that campaigns carry approval state. It stops short of describing pagination, limits, or error behavior.

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?

It is one dense run-on sentence plus a second sentence that re-lists the nine action values already implied in the first. The action enumeration duplicated in 'Actions: ...' is largely redundant with the enum, and the resource prose is hard to parse, though it is front-loaded with the domain and the membership requirement.

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 9-action dispatcher with a free-form nested 'params' object and no output schema, the description does a reasonable job: it covers the membership prerequisite, sketches what each action family returns, and points to 'help' for field-level detail. Deferring action-specific fields to a runtime help call is a legitimate design for this shape of tool, though it leaves the agent needing a second round trip.

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 75%, with the action enum and both id parameters documented in the schema itself, so the schema carries most of the burden. The description adds semantic shading (what 'get' vs 'preview' vs 'campaign_approval' conceptually return) but pushes all per-action field details to a runtime 'help' call rather than explaining them here.

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 resource domain (outreach to people at companies) and enumerates the concrete things it returns: threads, suggested people with drafted first emails, single messages, previews, and Mailbox campaigns. An agent can tell this is a read tool over outreach data. It does not, however, explicitly disambiguate from the sibling manage_outreach or send_email, which muddies selection slightly.

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?

There is a real precondition ('needs an Applystead membership') and a useful escape hatch ('Call with action "help" for each action's fields'), both of which help an agent proceed. But there is no explicit when-to-use routing: nothing tells the agent to pick this over manage_outreach for writes, or over get_mailbox/send_email for message delivery.

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.