Skip to main content
Glama

get_ai_build_job

Read-only

Status and result of a Build with AI job: created template/habit/program ids, check-in questions or onboarding form steps, summary, error and credits charged. Poll until status is no longer pending.

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": {
      "id": "<id>"
    },
    "name": "get_ai_build_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds genuinely new behavior: the job is asynchronous and must be polled until non-pending, and the result carries an error field plus credits charged. It does not explain terminal failure states or what to do when error is populated.

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?

Two sentences, front-loaded with what is returned and closed with the polling instruction. Since there is no output schema, the field enumeration earns its place rather than duplicating structured data, and there is no filler.

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

Completeness4/5

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

With no output schema, listing the returned fields and the pending-until-done semantics makes the definition largely self-sufficient for a read-only async job tool. The remaining gap is the lifecycle boundary: it doesn't say what a failed job looks like or whether a non-existent id errors, but nothing essential to invoking it is missing.

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?

A single required parameter 'id' is documented at 0% schema coverage. The description implies it identifies a Build with AI job, but never states the id's form, where it comes from (presumably start_build_with_ai), or that it is required — leaving the only parameter partly inferred.

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 names a specific verb+resource (status and result of a Build with AI job) and enumerates the returned artifacts: created template/habit/program ids, check-in questions or onboarding form steps, summary, error, credits charged. It does not, however, distinguish itself from the sibling get_build_with_ai_status, which an agent could plausibly confuse it with.

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?

It gives actionable usage context: 'Poll until status is no longer pending,' which tells the agent this is an async job and how to drive it to completion. It stops short of naming when to prefer it over get_build_with_ai_status, so no explicit alternative routing is provided.

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.