Skip to main content
Glama
suparse

Suparse MCP Server

Official
by suparse

Delete Documents

delete_documents

Remove unwanted documents from Suparse by specifying their document IDs. Clean up your document list efficiently.

Instructions

Delete one or more documents from Suparse by document ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_urlNoOptional API base URL. Defaults to SUPARSE_API_URL or Suparse production API.
document_idsYesSuparse document IDs to delete.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
deletedYes
document_idsYes
Behavior2/5

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

With no annotations, the description only says 'delete' which implies a destructive action but lacks details on whether it is hard/soft delete, impact on related resources, or error handling.

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?

A single, direct sentence with no redundancy or wasted words.

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

Completeness3/5

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

For a delete tool with two parameters, the description is minimal but functional. It does not mention the optional api_url parameter or the irreversible nature of deletion, but given the output schema exists, it is adequate.

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%, so parameters are already documented. The description adds only the phrase 'by document ID', which adds minimal meaning beyond the schema.

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 verb 'Delete' and the resource 'one or more documents from Suparse', specifying the method 'by document ID'. This distinguishes the tool from siblings like extract_file or list_templates.

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?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no note about irreversibility of deletion.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/suparse/suparse-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server