Skip to main content
Glama

Edit a queued message

edit_queued_message
Destructive

Use this when the user wants to change one message that has not gone out yet: its subject, its body, or when it is sent. The edit makes a new message with a new id and marks the old one as replaced. A message that already went out, or was skipped or declined, is refused. Free.

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": {
      "sendId": "<sendId>"
    },
    "name": "edit_queued_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoA new message, up to 20,000 characters, sent as written: tokens such as `{Contact First Name}` are filled in when a step's message is written, not in an edit.
sendIdYesThe queued message's `id`, as the campaign's queue lists it.
subjectNoA new subject line, up to 500 characters.
scheduledAtNoWhen to send it instead, as an ISO 8601 date-time in UTC.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, idempotentHint=false, and openWorldHint=true, but the description goes further and explains why: the edit creates a new message with a new id and marks the old one as replaced. That non-obvious copy-on-write consequence, plus the refusal behavior and the 'Free' cost note, is context an agent cannot get from the annotations alone.

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

Conciseness5/5

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

Three tight sentences lead with the use case, then the behavioral consequence, then the refusal and cost constraints. Nothing is padded; even the one-word 'Free.' carries distinct information.

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

Completeness5/5

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

For a destructive, non-idempotent mutation with full schema coverage, full annotations, and no output schema, the description supplies the missing pieces: the identity change (new id, old marked replaced), refusal conditions, and cost. An agent has everything needed to call it correctly and warn the user about the replacement.

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 100%, including the required sendId wording and the token-fill caveat on body, so the schema carries parameter meaning. The description only summarizes the editable fields and adds no syntax, format, or edge-case detail beyond that, making the baseline 3 correct.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('change one message that has not gone out yet') and enumerates the editable facets (subject, body, send time). It also separates this tool from state-adjacent siblings by declaring that messages already sent, skipped, or declined are refused, so an agent can route without opening the schema.

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 gives an explicit trigger condition ('Use this when the user wants to change one message that has not gone out yet') and explicit disqualifying states (already sent, skipped, declined). It stops short of naming a concrete alternative tool for those refused cases, so it falls just below the top band.

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