Skip to main content
Glama

AI3D Studio

by studio.ai3d
OverviewDiscussionsAdmin

Search my library

search_library
Read-onlyIdempotent

Search the Library of past generations kept by this account, newest first: filter by words in the prompt or title and by kind (3d, image, …). Returns the job id, model, status and result file URLs of each run. Use next_cursor to page. Only runs of this account are ever searched. For the full detail of one run call get_job.

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return, 1 to 50.
queryNoWords to look for in the prompt or title.
cursorNoThe next_cursor of the previous result.
media_typeNoOnly runs of this kind, e.g. '3d' or 'image'.

Output Schema

NameRequiredDescriptionDefault
itemsYes
totalYesHow many runs match in all.
next_cursorYesPass as cursor for the next page; null at the end.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed28 schema fields changed
    • removedOutput schema / properties / items / items / properties / created_at / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / items / items / properties / created_at / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / items / items / properties / files / items / properties / alternates / items / properties / source / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / items / items / properties / files / items / properties / alternates / items / properties / source / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / items / items / properties / files / items / properties / content_type / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / items / items / properties / files / items / properties / content_type / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / items / items / properties / files / items / properties / duration_seconds / anyOf
      Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / items / items / properties / files / items / properties / duration_seconds / type
      Added value: +[
+  "number",
+  "null"
+]
    • removedOutput schema / properties / items / items / properties / files / items / properties / format / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / items / items / properties / files / items / properties / format / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / items / items / properties / files / items / properties / height / anyOf
      Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / items / items / properties / files / items / properties / height / type
      Added value: +[
+  "number",
+  "null"
+]
    • removedOutput schema / properties / items / items / properties / files / items / properties / role / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / items / items / properties / files / items / properties / role / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / items / items / properties / files / items / properties / size_bytes / anyOf
      Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / items / items / properties / files / items / properties / size_bytes / type
      Added value: +[
+  "number",
+  "null"
+]
    • removedOutput schema / properties / items / items / properties / files / items / properties / thumbnail_url / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / items / items / properties / files / items / properties / thumbnail_url / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / items / items / properties / files / items / properties / width / anyOf
      Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / items / items / properties / files / items / properties / width / type
      Added value: +[
+  "number",
+  "null"
+]
    • removedOutput schema / properties / items / items / properties / prompt / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / items / items / properties / prompt / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / items / items / properties / scene / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / items / items / properties / scene / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / items / items / properties / title / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / items / items / properties / title / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / next_cursor / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / next_cursor / type
      Added value: +[
+  "string",
+  "null"
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value beyond that: result ordering (newest first), account scoping, the returned fields (job id, model, status, result file URLs), and cursor-based paging via next_cursor.

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?

Four compact sentences, front-loaded with what is searched and in what order, then return shape, paging and the sibling hand-off. No filler.

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?

Read-only search with a full output schema and complete annotation coverage; the description supplies scope, ordering, paging and the escalation path to get_job. Nothing needed to call it correctly is missing.

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

Parameters4/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 still adds useful framing by saying the query matches words in the prompt or title and that media_type selects a kind of run. Note a small naming drift: the prose says next_cursor while the parameter is cursor.

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?

Specific verb (search) plus a precisely scoped resource (the Library of past generations kept by this account), with ordering stated (newest first). It is clearly separable from get_job, which is named as the per-run detail tool.

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?

Explicitly names get_job as the alternative for full detail of a single run, and clarifies the scoping constraint that only this account's runs are searched. Lacks an explicit 'when not to use' clause (e.g. browse without query vs. query), but the routing context is clear.

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

All AI3D Studio toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources