Skip to main content
Glama

attachment_remove

Remove an attachment from a task or project by attachment ID. Provide the task or project ID along with the attachment ID. Call sync_trigger to apply changes.

Instructions

DEPRECATED — use attachment_delete instead (renamed for CRUD-verb consistency). Remove an attachment from a task or project by attachment ID. Do not use to retrieve or export attachment content — use attachment_save_to_path instead. Returns { removed: true, attachmentId, ownerKind, ownerName } — ownerKind is 'task' or 'project' and ownerName is captured BEFORE the JXA call so it survives even if the lookup were to fail post-mutation; null only when the parent itself has been deleted. The agent can describe the removal without a follow-up read. Throws NotFound if the attachment or owner does not exist. Permanent — cannot be undone. Mutations do not propagate until sync_trigger is called. Example: attachment_delete({ taskId: "abc123", attachmentId: "att456" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIdNoPersistent ID of the task that owns the attachment. Provide exactly one of taskId or projectId.
projectIdNoPersistent ID of the project that owns the attachment. Provide exactly one of taskId or projectId.
attachmentIdYesPersistent ID of the attachment to remove. Get from attachment_list.
Behavior5/5

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

No annotations provided, so description carries full burden. Discloses return object structure, null ownerName scenario, error behavior (NotFound), permanence, and sync trigger requirement. Comprehensive.

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?

Description is detailed but not unnecessarily long. Structured with purposeful sentences, though could be slightly more concise. Still earns its length with valuable information.

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

Completeness5/5

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

No annotations or output schema, yet description covers all critical aspects: purpose, deprecation, input constraints, return value, error cases, side effects, and sync note. Fully complete for the tool's complexity.

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 baseline 3. Description adds context: attachmentId source (attachment_list) and the mutual exclusivity of taskId/projectId, but schema already describes that. No additional meaningful parameter details beyond 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?

Description clearly states the tool removes an attachment by ID, distinguishes from retrieval and from the renamed sibling (attachment_delete). Verb+resource+scope are precise.

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

Usage Guidelines5/5

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

Explicitly marks deprecated with replacement (attachment_delete), and warns against using for retrieval (use attachment_save_to_path). Provides clear when/when-not guidance.

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/torsday/omnifocus-mcp'

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