Skip to main content
Glama

project_get_many

Fetch multiple OmniFocus projects by their IDs in a single call, returning up to 100 full project objects at once. Ideal for batch retrieval when you already have a list of project IDs.

Instructions

Fetch up to 100 projects by persistent ID in a single OmniFocus round-trip. Use when you have a set of project IDs and need full project objects for all of them. Do NOT use for a single ID — use project_get instead. Returns Project[] in input order. Missing IDs are omitted and appear in meta.warnings. Read-only; safe to retry. Example: project_get_many({ ids: ["prj123", "prj456"] })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesArray of project IDs to fetch (0..100). Get IDs from project_list. Missing IDs are omitted (not errors) and appear in meta.warnings.
fieldsNoRestrict each returned project to this list of top-level fields (id is always returned). Omit for the full project shape. Empty array returns just id. Unknown names are dropped silently and surface in meta.warnings.WARN_UNKNOWN_FIELDS. Allowed: name, note, noteHtml, folderId, tagIds, status, completionCriterion, deferDate, deferDateFloating, dueDate, dueDateFloating, estimatedMinutes, flagged, reviewIntervalDays, nextReviewDate, lastReviewDate, completed, completedAt, dropped, droppedAt, taskCount, completedTaskCount, createdAt, modifiedAt, _links.
maxOutputBytesNoCap the serialized byte size of the returned projects[] array. When the response would exceed this, the server returns as many whole projects as fit (in input order), sets meta.truncatedAtCap=true with meta.bytesReturned and meta.itemsReturned, and lists the trimmed ids in meta.warnings.WARN_RESULT_TRUNCATED details.droppedIds — re-request those in a smaller batch or with a higher cap. Omit for no cap. Values above the server's hard ceiling (~1 MiB) are clamped. A single project larger than the cap is still returned whole so the batch always makes progress.
Behavior5/5

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

Discloses key behavioral traits: returns projects in input order, omits missing IDs with warnings in meta.warnings, and states it is read-only and safe to retry. For the maxOutputBytes parameter, it explains truncation behavior in detail, which is not obvious from the schema alone.

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 compact and front-loaded: the first sentence states the core purpose, followed by usage guidelines, behavioral notes, and an example. No extraneous information; every sentence serves a purpose.

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 the absence of an output schema, the description adequately explains the return type (Project[] in input order) and mentions meta.warnings for missing IDs. The fields parameter and maxOutputBytes are well-described. Minor gap: it doesn't explicitly state that the 'fields' parameter affects each returned project's shape, but this is implied by the parameter description. Overall, the tool is well-documented for an agent.

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

Parameters4/5

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

Schema description coverage is 100% for the two parameters (ids and fields), so baseline is 3. However, the description adds significant value beyond the schema: it clarifies the purpose of 'fields' (restrict returned fields), explains the behavior of maxOutputBytes (truncation, progress guarantee), and provides an example. This additional context justifies a score above baseline.

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 fetches up to 100 projects by persistent ID in a single round-trip, distinguishing it from project_get (single ID) and project_list (all projects). The verb 'Fetch' and resource 'projects by ID' are specific and actionable.

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 provides when to use (multiple IDs) and when not to (single ID, recommending project_get instead). Includes an example usage, making the guidance concrete and easy to follow.

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