Skip to main content
Glama

ai_modeling_canvas_lab_jobs

Read-only

Lists 3D Lab creative jobs for a specified node, with an optional result limit, so you can inspect job history and status for that node.

Instructions

List 3D Lab creative jobs for a node.

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": {
      "nodeId": "<nodeId>"
    },
    "name": "ai_modeling_canvas_lab_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
nodeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. Beyond that the sentence only adds that results are scoped per node; it says nothing about ordering, whether results are paginated or truncated by the limit default, whether jobs from deleted nodes appear, or what a "creative job" record contains.

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?

A single front-loaded fragment with zero filler, so nothing is wasted. The trade-off is that it is arguably too compressed, packing scope into one clause rather than structuring purpose and constraints separately.

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

Completeness2/5

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

With no output schema, the description is the only place a caller can learn what comes back, and it does not say. For a listing tool with a pagination parameter, missing coverage of result shape, ordering and limit behavior leaves real gaps even though the operation is a simple read.

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 description coverage is 0%, so the description must carry parameter meaning and largely does not. "For a node" weakly implies nodeId is a canvas node identifier, but the limit parameter (default 20, max 100) and its pagination/truncation semantics are entirely undocumented, as is the accepted nodeId format.

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?

"List 3D Lab creative jobs for a node" gives a concrete verb (List) and resource (3D Lab creative jobs) with an explicit scope (for a node), which is clear enough to separate it from single-item siblings like ai_modeling_canvas_lab_job_get. It stops short of naming any sibling or stating the boundary explicitly, so it is clear but not differentiating on its own.

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?

There is no when-to-use or when-not-to-use guidance, no mention of the alternative single-job or cancel tools, and no note on when a caller should prefer the canvas-level job listing. The reader must infer usage purely from the name and the required nodeId.

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

Deploy Server

Other Tools