Skip to main content
Glama

Edit a message by hand

edit_outreach_message
Idempotent

Saves the user's own text of one message step (free). result_id and expected_revision from get_outreach_lead protect against an edit made meanwhile. [REST: PATCH /api/tasks/{id}/outreach/leads/{cid}/steps/{step_id}]

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>",
      "step_id": "<step_id>",
      "text": "<text>"
    },
    "name": "edit_outreach_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
cidYesThe person's id (cid) from list_leads.
textYes
step_idYesThe step id of the message (get_outreach_lead steps[].step_id).
task_idYesThe search id (task id), e.g. from list_searches or create_search.
result_idNo
expected_revisionNo

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 already declare non-read-only, idempotent, non-destructive. The description adds two things annotations cannot: the operation is free (no credit spend) and result_id/expected_revision act as an optimistic-concurrency guard against a concurrent edit. It does not say what happens when the revision check fails, which is the main remaining gap.

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?

Two tight sentences with the core action and cost front-loaded, followed by the concurrency note. The trailing REST endpoint is mildly extraneous for an agent but is compact and does not bury the important content.

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 mutation tool with annotations and no output schema, the description covers cost, concurrency safety, and parameter provenance. Only the failure behavior on a stale revision and whether text fully replaces prior content are unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%, and the description compensates by explaining the two undocumented parameters: result_id and expected_revision exist to protect against a concurrent edit. The other four parameters are documented in the schema itself, so the combined picture is nearly complete.

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: saving the user's own text for one message step. The parenthetical '(free)' and 'user's own text' implicitly separate it from the AI-rewrite siblings, though no sibling is named 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?

Implies the use case (manual editing instead of AI rewriting, at no cost) and points to get_outreach_lead as the source of result_id and expected_revision. It never states explicitly when to prefer this over rewrite_message or apply_message_variant, so the routing is left to inference.

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