Skip to main content
Glama
someposer
by someposer

list_tags

Retrieve all tags in OmniFocus to organize and manage tasks effectively. Use this tool to streamline task categorization and enhance workflow automation within the MCP OmniFocus server.

Instructions

List all tags in OmniFocus.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'list_tags', registered with @mcp.tool decorator. Delegates to the omnifocus utility function.
    @mcp.tool
    def list_tags() -> list[dict[str, str]]:
        """List all tags in OmniFocus."""
        return omnifocus.list_tags()
  • Core helper function implementing list_tags logic using JavaScript evaluation to fetch tags from OmniFocus, including hierarchical names.
    def list_tags() -> list[dict[str, str]]:
        """List all tags in OmniFocus.
    
        Returns:
            A list of dictionaries containing tag names and ids, with full hierarchical names.
        """
        script = Template(
            dedent("""
        ${__common_functions__}    
        
        (() => {
            return flattenedTags.map(tag => {
                return {
                    id: tag.id.primaryKey,
                    name: tag.name,
                    fullName: getFullTagName(tag),
                };
            });
        })();
        """)
        )
    
        return evaluate_javascript(script.substitute(__common_functions__=__common_functions__))
Behavior2/5

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

No annotations are provided, so the description carries full burden. While 'List all tags' implies a read-only operation, it doesn't disclose behavioral traits like whether it returns all tags at once or uses pagination, what format the output takes, or any rate limits or authentication requirements. The description is minimal and lacks necessary context for safe use.

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 a single, clear sentence with zero wasted words. It's front-loaded with the core purpose and efficiently communicates the essential action without unnecessary elaboration, making it easy to parse quickly.

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

Completeness3/5

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

Given the tool's simplicity (0 parameters, no output schema) and lack of annotations, the description is minimally adequate but incomplete. It states what the tool does but omits details like output format or behavioral constraints that would help an agent use it correctly. For a read-only list operation, this is borderline viable but leaves gaps.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't mention parameters, and since there are none, it doesn't need to compensate for any gaps. This meets the baseline for tools with no parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('List') and resource ('tags in OmniFocus'), making the purpose immediately understandable. It distinguishes from siblings like 'list_tasks_by_tag' by focusing on tags themselves rather than tasks filtered by tags. However, it doesn't specify scope or format details that would make it fully distinctive.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'list_tasks_by_tag' that also involve tags, there's no indication whether this tool should be used for browsing all tags versus filtering tasks by tags, or any prerequisites for its use.

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

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

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