Skip to main content
Glama

Social0

reply_to_dm

Destructive

Send a message into an existing DM conversation. Social0 verifies the conversation belongs to the account before sending. This delivers a real message to a real person; confirm the wording with the user first.

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": {
      "conversation_id": "<conversation_id>",
      "account": "<account>",
      "text": "<text>"
    },
    "name": "reply_to_dm"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesMessage text
accountYesConnected account UUID or platform name that owns the conversation
peer_idNo
media_idNoMedia upload ID. X accepts image and video, TikTok image only, Bluesky text only.
conversation_idYesconversation_id from list_inbox_dms

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, but the description adds real value by explaining the ownership-verification step and warning that this sends an irreversible, real message to a real person requiring user confirmation. It leaves idempotency unstated, which matters given idempotentHint=false (a retry sends twice).

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 short sentences, front-loaded with the action, then the safety/verification behavior, then the user-confirmation requirement. No filler or repetition.

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?

No output schema exists, and the description covers the off-call risks an agent most needs for a destructive, open-world send: verification, real delivery, and confirmation. It does not address failure behavior or duplicate-send risk, which are the remaining gaps for a non-idempotent mutation.

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 80 percent, so the schema already documents text, account, conversation_id, and media_id. The description reinforces the conversation constraint ("existing DM conversation"), but the undocumented peer_id remains unexplained in both places, keeping this just above baseline rather than higher.

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 target: "Send a message into an existing DM conversation." The word "existing" cleanly separates it from draft-creation siblings such as create_draft, 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Makes the precondition clear (the conversation must already exist, with conversation_id sourced from list_inbox_dms per the schema) and adds an explicit operator instruction to confirm wording with the user first. It does not explicitly point to an alternative tool, so it stops short of full routing 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.