Skip to main content
Glama

attachment_add

Add a file attachment to a task or project by specifying a local file path. The file is embedded into the database and returns the new attachment's ID and owner details.

Instructions

DEPRECATED — use attachment_create instead (renamed for CRUD-verb consistency). Add a file attachment to a task or project from a local file path. The file is embedded into the OmniFocus database. Path must be within the allowed scope (default: $HOME; override via OMNIFOCUS_ATTACHMENT_PATHS). File must not exceed the size cap (default 100 MB; override via OMNIFOCUS_MAX_ATTACHMENT_MB). Returns { id, ownerKind, ownerName } — ownerKind is 'task' or 'project' and ownerName is the parent's display name (null only if the parent was deleted between the add and the lookup) so the agent can describe the new attachment without a follow-up read. Mutations do not propagate until sync_trigger is called. Example: attachment_create({ taskId: "abc123", filePath: "/Users/me/report.pdf" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIdNoPersistent ID of the task that owns the attachment. Provide exactly one of taskId or projectId.
filePathYesAbsolute path to the source file to attach. Must be within the allowed attachment path scope.
projectIdNoPersistent ID of the project that owns the attachment. Provide exactly one of taskId or projectId.
Behavior4/5

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

With no annotations, the description provides behavioral details: file is embedded into database, path scope and size caps, return shape including edge case (null if parent deleted), and sync_trigger requirement. Somewhat thorough for a deprecated tool.

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 a single paragraph but efficiently conveys deprecation, purpose, constraints, and return value. No redundancy, but could be slightly more structured.

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?

Given deprecation, the description covers enough for an agent to understand the tool's behavior, constraints, and output. The return shape is detailed. Completeness is high for a tool not intended for new use.

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 is 3. Description adds context on path scope and size cap but does not fully explain mutual exclusivity of taskId/projectId beyond schema. Adequate but not exceptional.

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?

Clearly states the tool is deprecated and renamed to attachment_create. It specifies the action (adds a file attachment) and resource (task or project). Distinguishes from sibling attachment_create as the replacement.

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 advises not to use this tool (DEPRECATED) and directs to use attachment_create instead. Provides clear when-not and alternative.

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