Skip to main content
Glama

Get application jobs

get_application_jobs
Read-only

Get an Application's platform job history (create/update/reconcile jobs with status and timing). Use this to see what the platform has been doing to the application. Read-only.

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": {
      "application_id": "<application_id>"
    },
    "name": "get_application_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number (default 1).
page_sizeNoPage size (default 20, max 100).
application_idYesThe Application's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

readOnlyHint=true already tells the agent this is a safe read, and the description adds real context beyond that: it identifies which job categories appear in the history and that status and timing are included. The trailing "Read-only" is redundant with the annotation, and pagination/sort behavior is left unstated, but the added detail is substantive.

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 purpose, then use case, then safety. Nothing is padding except the redundant "Read-only" that duplicates the annotation.

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?

For a simple paginated read tool with full schema coverage and no output schema, the description is roughly adequate but leaves gaps: it does not say how results are ordered, how far back history goes, or that responses are paginated and should be iterated. An agent could call it correctly but would not know what shape or volume of data to expect.

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 description coverage is 100%, so application_id, page, and page_size are fully documented in the schema itself. The description adds no parameter-level meaning (no note on paging through long histories), so this sits at the baseline.

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 gives a specific verb and resource ("Get an Application's platform job history") and narrows the scope with a parenthetical naming the job kinds (create/update/reconcile) plus the fields returned (status and timing). That said, it never distinguishes itself from nearby siblings such as get_jobs or get_application_workflow_run_jobs, which an agent could easily confuse with this one.

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

Usage Guidelines3/5

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

"Use this to see what the platform has been doing to the application" supplies a use case, but there is no explicit when-not guidance and no named alternative for workflow-run jobs or the general get_jobs tool. Usage is implied rather than routed.

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.