Skip to main content
Glama
talhaorak

Taiga MCP Bridge

by talhaorak

delete_attachment

Delete an attachment from a user story, task, issue, epic, or wiki page by providing its ID and object type.

Instructions

Delete an attachment by its ID. object_type: 'user_story', 'task', 'issue', 'epic', or 'wiki_page'. Uses default session if session_id not provided.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
attachment_idYes
object_typeYes
session_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Discloses session handling (default session) and destructive nature, but lacks details on permanence, authorization needs, or return value. No annotations to supplement.

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?

Two sentences, front-loaded with action and resource, second sentence adds essential parameter context. No wasted words.

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?

For a deletion tool with 3 parameters and an output schema, the description is too brief. Missing parameter details (e.g., format of attachment_id), behavioral info, and output description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so description should compensate. It explains object_type options but provides no additional meaning for attachment_id or session_id beyond what schema offers.

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?

Clearly states verb 'delete' and resource 'attachment', with explicit list of valid object_types. Distinguishes from siblings like delete_epic by dealing with attachments, not the entities themselves.

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

Usage Guidelines3/5

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

Implies usage when deleting an attachment, but provides no explicit guidance on when to use vs alternatives, prerequisites, or conditions. No exclusions mentioned.

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/talhaorak/pytaiga-mcp'

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