Skip to main content
Glama
Sign In
cueapi-mcp

cueapi-mcp

Official
by cueapi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

cueapi_delete_cue

Remove a CueAPI cue permanently using its ID. This action is irreversible and deletes the cue from the system.

Instructions

Delete a cue permanently. Irreversible.

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": {
      "cue_id": "<cue_id>"
    },
    "name": "cueapi_delete_cue"
  }
}

Input Schema

NameRequiredDescriptionDefault
cue_idYesCueAPI cue ID (e.g. 'cue_...')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively communicates critical traits: the operation is destructive ('Delete'), permanent, and irreversible. This covers safety concerns, though it lacks details on permissions, error handling, or side effects like cascading deletions.

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 extremely concise and front-loaded, consisting of only two sentences that directly convey the core action and its critical implication. Every word earns its place, with no redundancy or unnecessary elaboration.

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?

For a destructive tool with no annotations and no output schema, the description provides essential context on permanence and irreversibility, which is crucial for safe usage. However, it lacks information on return values or error conditions, leaving some gaps in operational understanding.

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 schema description coverage is 100%, with the parameter 'cue_id' fully documented in the schema. The description does not add any parameter-specific information beyond what the schema provides, such as format examples or validation rules, so it meets the baseline for high schema coverage.

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 clearly states the specific action ('Delete') and target resource ('a cue'), with the adverb 'permanently' emphasizing the nature of the operation. It directly distinguishes from sibling tools like 'cueapi_pause_cue' or 'cueapi_resume_cue' by indicating a destructive removal rather than a state change.

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?

The description implies usage context through 'permanently' and 'Irreversible,' suggesting this tool should be used for final removal rather than temporary actions. However, it does not explicitly name alternatives (e.g., 'cueapi_pause_cue' for temporary suspension) or state when not to use it, such as for partial updates.

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