Skip to main content
Glama
Sign In
send16-mcp

send16-mcp

by spruikco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

delete_action

Remove a specific action by providing its action ID. Use this tool to clean up or manage actions in your Send16 account.

Instructions

Delete an Action.

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": {
      "actionId": "<actionId>"
    },
    "name": "delete_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyNoSend16 API key (overrides SEND16_API_KEY env var)
actionIdYesAction ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.7

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided. Description only repeats the tool's name without disclosing behavioral traits like destructiveness, permissions, or side effects beyond what the name implies.

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?

Very concise single sentence with no waste. However, it lacks any structural elements like front-loading key info, but it is appropriately short for a simple delete tool.

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

Completeness2/5

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

Given no annotations or output schema, the description is too minimal. It does not explain what an action is, prerequisites, side effects, or error conditions, which are needed for completeness.

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%, so the schema already documents both parameters. The description adds no additional meaning beyond the schema, meeting the baseline of 3.

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 'Delete an Action.' clearly states the action and resource. It distinguishes from siblings like create_action, update_action, and get_action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance on when to use vs alternatives. No exclusions, prerequisites, or context for using this tool over siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools