Skip to main content
Glama

Edit the sender card

edit_sender_card
Idempotent

Correct the sender's card the analysis made (name, role, company, voice = how they write, summary, background, interests). [REST: PATCH /api/tasks/{id}/outreach/sender/card]

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": "edit_sender_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
roleNo
voiceNo
companyNo
summaryNo
task_idYesThe search id (task id), e.g. from list_searches or create_search.
interestsNo
backgroundNo
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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds the REST verb (PATCH), which implies a partial update, but it never says whether omitted fields are preserved, what happens when the card does not yet exist, or how generation_id scoping affects the write.

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

Conciseness4/5

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

A single front-loaded sentence lists the editable surface with no filler, and the trailing bracketed REST note is compact. The bracketed endpoint is developer metadata that adds little for an agent, but it costs almost nothing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a 9-parameter mutation tool with 22% schema coverage and no output schema, so the description should do more. It covers the field list adequately but leaves update semantics, generation_id's role, and success/failure behavior unaddressed.

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 description coverage is only 22%, so the description carries real weight here: it names the seven editable fields and usefully explains 'voice = how they write', which the schema does not. However, the array parameters (background, interests) and generation_id get no semantic explanation, and nothing is said about partial-update semantics for the listed fields.

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 gives a specific verb ('Correct') plus a specific resource ('the sender's card the analysis made') and enumerates exactly which fields are editable. An agent can tell it apart from generic tools, though it never names the adjacent sibling set_outreach_sender, so the boundary with that tool must be inferred.

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 rather than stated: 'the analysis made' signals this is for fixing auto-generated card content. There is no explicit when-to-use, no exclusion, and no reference to alternative tools such as set_outreach_sender, which an agent would plausibly confuse this with.

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