Skip to main content
Glama

Typebar (formerly SuperDocs)

get_session_jobs

Returns the full job history of one document. Useful for auditing what the AI did to a document over time, or finding a specific job that's waiting for HITL approval. Same shape as list_jobs but scoped to one session.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>"
    },
    "name": "get_session_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of jobs to return
compactNoWhen true, omit each job's heavy result body + streamed intermediate events — returns just status/progress/ids/timestamps. Recommended for agents listing many jobs.
session_idYes

Output Schema

NameRequiredDescriptionDefault
jobsYesArray of job details.
totalYesTotal number of jobs returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does not meet it. It claims a 'full job history' while the schema defaults limit to 20, so the promise of completeness is misleading with no mention of truncation or pagination. It also contradicts itself on the scoping key (document vs session), which directly affects how the agent identifies the resource.

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?

Three short sentences, front-loaded with the core behavior and followed by use cases. Slightly wasteful in that the first sentence and last sentence disagree about scope rather than reinforcing each other.

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?

An output schema exists, so return shape needn't be re-explained, and calling it correctly requires only a session_id. Still missing for a history/listing tool: pagination or limit semantics, what happens for an unknown session, and how it relates to get_job/get_session_history.

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

Parameters2/5

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

Schema coverage is 67%: limit and compact are well documented in the schema, but session_id has no schema description, so the description is the only source of meaning for it — and it gives conflicting signals ('one document' vs 'scoped to one session'). The description never mentions limit or compact, so the default-20 truncation trap and the compact recommendation stay buried in the schema.

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

Purpose3/5

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

The verb and resource ('Returns the full job history') are clear, and the final sentence distinguishes it from list_jobs by scope. However the description opens by saying it covers 'one document' while the required parameter and closing sentence say session — an agent cannot tell whether to pass a document ID or a session ID, which undermines an otherwise clear purpose.

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?

Two concrete use cases are given (auditing AI actions over time, locating a job awaiting HITL approval), which tells the agent when to reach for this tool. It also names list_jobs as the broader alternative. It stops short of exclusions: nothing says to use get_job for a single job lookup or list_jobs when no session is known.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.