Skip to main content
Glama

import_opml

Import tasks from OPML XML into OmniFocus, recreating the task hierarchy and preserving due dates, defer dates, and flagged state.

Instructions

Import tasks from an OPML XML string into OmniFocus. Parses the OPML produced by export_opml and recreates the task hierarchy. Top-level elements are matched to existing projects by OmniFocus ID (for round-trip) then by name; unmatched project outlines land in the Inbox. LOSSY: due dates, defer dates, and flagged state are preserved; tags, notes, attachments, and repetition rules are silently dropped (not encoded in OPML). Do NOT use to export data; prefer export_opml for that. Returns { imported, tasks: [{ id, name }] } — imported is the count of tasks created and tasks pairs each new id with its display name (resolved via a single getTasksMany batch, no N+1) so the agent can confirm what landed without a follow-up read. Orphan ids (rare; the task was deleted between import and lookup) are dropped from the array. Writes to OmniFocus; call sync_trigger after import to propagate changes to other devices. Example: import_opml({ opml: "..." })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opmlYesWell-formed OPML XML string to import. Use the output of export_opml for a round-trip.
destinationProjectIdNoWhen set, all tasks are created in this project regardless of project headings in the OPML. Get the ID from project_list. Omit to match projects by ID/name from the OPML structure.
Behavior5/5

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

Discloses round-trip matching logic (by ID, then by name), lossy behavior (preserved: due dates, defer dates, flagged; dropped: tags, notes, attachments, repetition), return format, orphan handling, and write nature. No annotations provided, so description carries full burden and does so comprehensively.

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 dense but efficient; front-loaded with main purpose and structure. Every sentence adds value, though slight length could be trimmed slightly without losing content.

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?

Covers all aspects: input format, matching, lossy fields, return structure (imported count, tasks array with id/name), orphan handling, and required follow-up sync trigger. No output schema exists, so description fully compensates.

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 coverage is 100%, but description adds context: opml parameter notes 'Well-formed OPML XML string' and recommends using export_opml output; destinationProjectId explains override behavior and source for project ID. Adds meaning beyond schema's brief descriptions.

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 action (import), resource (tasks from OPML string), and destination (OmniFocus). It specifies it parses OPML from export_opml and recreates hierarchy, distinguishing it from export_opml and import_taskpaper.

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 warns against using for export ('Do NOT use to export data; prefer export_opml for that') and instructs to call sync_trigger after import to propagate changes. Also mentions when to omit destinationProjectId for matching by ID/name.

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