Skip to main content
Glama

Decline queued messages

decline_queued_messages
DestructiveIdempotent

Use this when the user does not want queued messages sent. Declines up to 100 messages that are waiting for approval or scheduled: they are not sent, and each person's sequence in that campaign ends. Messages that already went out are reported as ignored. 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": {
      "sendIds": "<sendIds>"
    },
    "name": "decline_queued_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
sendIdsYes1 to 100 queued messages, each once, by the `id` the queue lists.

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?

The description adds substantial behavior beyond the annotations: it explains that the sequence ends for each affected person, that already-sent messages are reported as ignored, and that the operation is free. These details clarify consequences of this destructive, non-read-only action.

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?

The description is front-loaded and compact, with no wasted sentences. Each sentence adds useful context about usage, effects, ignored messages, or cost.

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 simple one-parameter mutation without an output schema, the description covers usage condition, limits, side effects, ignored-message behavior, and cost. An agent has enough information to invoke 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?

The single parameter is fully documented in the schema, including the 1-100 limit, uniqueness, and ID format. The description restates the up-to-100 limit but does not add notable meaning beyond the schema text.

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 uses a specific verb and resource: declining queued messages. It also states the scope and effect clearly, including that declined messages are not sent and the person's campaign sequence ends.

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 a clear triggering condition: use when the user does not want queued messages sent. It does not explicitly name alternatives such as approving, skipping, or editing queued messages, so it stops short of full when-not/alternative 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