Skip to main content
Glama

plugin_invoke

Invoke an installed Omni Automation plug-in in OmniFocus by its bundle identifier, with an optional argument.

Instructions

Invoke a named Omni Automation plug-in action in OmniFocus. Use this when you need to run a specific installed plug-in — not for built-in OmniFocus operations. Do NOT use to run arbitrary JavaScript; for raw scripting use run_omnijs_script (requires opt-in env var). identifier is the plug-in's bundle ID (e.g. "com.example.my-plugin"). arg is an optional JSON-serialisable value passed to the plug-in action as Action.args[0]. Returns { result } where result is the plug-in's return value (arbitrary JSON). Throws NotFound if the plug-in is not installed. Side effects: plug-in may mutate OmniFocus data; call sync_trigger if you need changes on other devices. Example: plugin_invoke({ identifier: "com.example.my-plugin" }) Example: plugin_invoke({ identifier: "com.example.my-plugin", arg: { mode: "export" } })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argNoOptional JSON-serialisable argument forwarded to the plug-in action as Action.args[0]. Defaults to null.
identifierYesBundle identifier of the Omni Automation plug-in to invoke (e.g. "com.example.my-plugin").
Behavior5/5

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

Despite no annotations, description fully discloses side effects (may mutate data, need sync_trigger for multi-device changes), error behavior (throws NotFound), and return format ({ result }).

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?

Well-structured with front-loaded main action, but slightly verbose; could be trimmed while retaining all key info.

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: purpose, usage, parameters, side effects, errors, return value, and examples. No output schema needed as return format is explained.

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

Parameters5/5

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

Schema coverage is 100%, but description adds meaning: explains identifier as bundle ID with example, and arg as optional JSON-serialisable forwarded to Action.args[0], providing context 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?

Clearly states the tool invokes a named Omni Automation plug-in action in OmniFocus, with specific verb and resource. Distinguishes from sibling tool run_omnijs_script for raw JavaScript execution.

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 states when to use (specific installed plug-in) and when not to use (not for built-in operations, not for arbitrary JavaScript). Points to alternative run_omnijs_script and explains parameters with examples.

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