Skip to main content
Glama

Set the sender

set_outreach_sender

Who writes the messages: mode=linkedin with the sender's LinkedIn link (the profile and posts are analysed, about a minute), or mode=text with a few sentences about them. The first paid setup step of a generation spends its brief. Then poll get_outreach. [REST: PUT /api/tasks/{id}/outreach/sender]

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

Input Schema

NameRequiredDescriptionDefault
modeYes
textNo
task_idYesThe search id (task id), e.g. from list_searches or create_search.
linkedin_urlNo
generation_idNoThe outreach generation id (get_outreach campaign.generation.id); omitted: the current one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only cover the mutation/safety profile, and the description adds genuinely new behavior: this is a paid step that consumes credits, LinkedIn analysis takes about a minute, and the agent must poll get_outreach for completion. It stops short of saying what happens on repeat calls, even though idempotentHint is false.

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 mode pairing is front-loaded and efficient, but the sentence 'The first paid setup step of a generation spends its brief' is jargon-heavy and obscures the important cost meaning. The trailing REST endpoint note is compact but low value for an agent choosing the tool.

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 mutation with no output schema and partial schema coverage, the description supplies the key missing context: cost, latency, and the required follow-up call. It omits overwrite/repeat-call behavior and error conditions, which are the remaining gaps for a mutating tool.

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?

With 40% schema coverage, the description compensates well for the two conditional parameters: it defines what mode=linkedin versus mode=text expects and implies the matching linkedin_url/text fields. task_id and generation_id are left entirely to the schema, so the conditional-requirement gap (which field is mandatory per mode) is only implied, not stated.

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 identifies the resource ('Who writes the messages') and spells out the two operating modes with their inputs (LinkedIn link vs. a few sentences), so an agent can tell this configures the outreach sender by mode. The verb 'set' comes only from the name/title rather than the prose, which keeps it just 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 Guidelines4/5

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

It clearly states the two mutually exclusive paths — mode=linkedin with a link, mode=text with sentences — and adds sequencing guidance ('Then poll get_outreach'), which tells the agent what to do next. It does not distinguish this from the related card-editing step, so there is no explicit when-not guidance.

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