Skip to main content
Glama

Skip a queued message

skip_queued_message
DestructiveIdempotent

Use this when one queued message should not be sent but the person should stay in the campaign. The message is skipped and the person moves on to their next step. Skipping a message that is already skipped changes nothing. One that already went out, was declined or was replaced by an edit 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": "skip_queued_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
sendIdYesThe queued message's `id`, as the campaign's queue lists it.

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 destructive/idempotent, but the description adds real behavior: the person advances to their next step, re-skipping is a no-op, and three message states are refused outright. It also discloses cost ('Free'), which no annotation carries.

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?

Four short sentences, front-loaded with the decision rule, followed by effect, idempotency, refusal cases, and cost. Nothing is padded or repeated.

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?

A one-parameter, non-open-world tool with no output schema and full annotation coverage; the description covers trigger, effect, edge cases, and cost. An agent has everything needed to call it correctly.

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 100% and the single sendId parameter is well documented there as the queue-listed id, so the description adds nothing parameter-specific. Baseline 3 applies when the schema does the heavy lifting.

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 ('one queued message should not be sent') and pins the scope with the key qualifier 'but the person should stay in the campaign', which is exactly what separates it from decline_queued_messages. An agent can decide between skip and decline without opening either 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 when-to-use condition ('one queued message should not be sent but the person should stay in the campaign') plus when-not conditions (already sent, declined, or replaced by an edit is refused). It never names the sibling to use instead when the person should leave the campaign, so the alternative is only implied.

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