Skip to main content
Glama

comfyui_get_history

Read-onlyIdempotent

Retrieve paginated ComfyUI execution history to review past jobs and workflow runs. Supports offset and limit for browsing arbitrarily far back, returning paged results with a has_more flag.

Instructions

Browse ComfyUI execution history (read-only).

    Uses server-side `/history?offset=N&max_items=M` so callers can page
    arbitrarily far back. The tool requests one extra entry per page so it
    can set ``has_more`` without an additional round-trip.

    Args:
        limit: Maximum number of results to return (default: 25, max: 100)
        offset: Zero-based starting index (default: 0)

    Returns:
        Envelope with keys ``items``, ``count`` (items in this page),
        ``offset``, ``limit``, ``has_more``, and ``total``.

        ``total`` is set only when we can prove the true count:

        - ``offset + count`` on the last page when ``count > 0``
          (the upstream returned at most ``limit`` entries, so we've seen
          everything from ``offset`` onward).
        - ``0`` when ``offset == 0`` and the upstream returned nothing
          (history is genuinely empty).
        - ``None`` otherwise (``has_more`` is True, OR we paged past the
          end and got back an empty result — in the latter case the true
          count is somewhere in ``[0, offset]`` and we can't tell which).

        ``has_more`` is the canonical end-of-history signal.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return (1-100, default varies by tool).
offsetNoZero-based starting index for pagination.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

The description goes well beyond the annotations, explaining server-side pagination, the extra entry request for has_more, and detailed edge cases for total. This reveals significant behavioral traits (such as round-trip optimization and total's conditional semantics) that are not in the annotations.

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 well-structured with clear sections for purpose, behavior, args, and returns. It is detailed but every sentence earns its place, especially the bullet-pointed return semantics. The front-loaded first sentence immediately conveys the tool's core purpose.

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?

Given the tool's complexity, the description is thorough: it explains pagination, return envelope keys, and all edge cases for total and has_more. The output schema exists but the description goes beyond it, making the tool fully understandable for an agent.

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 the baseline is 3. The description only restates the parameter defaults and ranges already present in the schema, adding no new semantic meaning beyond what is already structured.

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?

The description clearly states the tool browses ComfyUI execution history in a read-only manner. The verb 'Browse' is specific and the resource 'execution history' is distinct from sibling tools like get_queue or get_job, making the purpose unambiguous.

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

Usage Guidelines4/5

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

While no explicit alternatives are mentioned, the description provides clear context that this tool is for read-only browsing of execution history, which distinguishes it from mutating tools. However, it does not explicitly say when not to use it or mention alternatives like get_job.

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/hybridindie/comfyui_mcp'

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