Skip to main content
Glama

Emero

by io.github.EmeroAI
OverviewDiscussionsAdmin

List project creations

list_project_creations

Widget-only (the inline creation widget calls it; the assistant never does). Returns the 12 newest creations in this chat's project with their status, embedded thumbnails and links, so the widget can render and live-refresh its tiles. Read-only. To find past work by description across every project, use search_creations instead.

Input Schema

NameRequiredDescriptionDefault
haveNoCreation ids the widget already shows thumbnails for. Their thumbnails and links are skipped in the reply to keep refreshes light. Omit on the first load.
project_idNoOpaque per-chat project id: "p-" plus 6 random letters and digits. Every chat is a new project. Mint one on your first emero call and pass that SAME id on every call in this chat. Never mint a second one in the same chat, even for a new topic, campaign or subject. Only when the user asks to continue an earlier project, reuse its id from get_emero_brain's project list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / have / description
      Added value: +"Creation ids the widget already shows thumbnails for. Their thumbnails and links are skipped in the reply to keep refreshes light. Omit on the first load."
    • changedInput schema / properties / project_id / description
      Previous value: -"Opaque per-chat project id. Mint one on your first emero action, pass that SAME id every call. One project per chat: NEVER mint a second for a new topic/campaign/subject/vibe — all stay in the one project; a new id is only for a new chat (server folds a stray id back in). A new chat the user says continues an earlier project reuses that project's id (from get_emero_brain's project list)."New value: +"Opaque per-chat project id: \"p-\" plus 6 random letters and digits. Every chat is a new project. Mint one on your first emero call and pass that SAME id on every call in this chat. Never mint a second one in the same chat, even for a new topic, campaign or subject. Only when the user asks to continue an earlier project, reuse its id from get_emero_brain's project list."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does state read-only, the 12-item cap, the returned fields (status, embedded thumbnails, links), and that refreshes are live/lightweight. It does not cover failure modes or how skipping works beyond what the schema says, keeping it just short of 5.

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?

Three short sentences, front-loaded with the caller constraint that determines whether an agent should use it at all, followed by return contents and the alternative. Nothing is padding.

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?

There is no output schema, yet the description says exactly what comes back (status, thumbnails, links, 12 newest) so an agent need not guess. Combined with fully documented parameters, nothing required to call or interpret 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?

Schema coverage is 100%: both 'have' and 'project_id' are fully documented in the schema, including the skipping behavior and project-id minting rules. The description only hints at refresh behavior ('live-refresh its tiles'), so the schema does the heavy lifting and a baseline 3 is appropriate.

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?

States a specific verb and resource plus precise scope: the 12 newest creations in this chat's project, with status, thumbnails and links. It also declares the caller boundary (widget-only, the assistant never calls it), which distinguishes it cleanly from siblings.

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

Usage Guidelines5/5

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

Explicitly says who calls it (the inline creation widget) and who does not (the assistant), and names the alternative for the other job: use search_creations to find past work by description across every project. When-to-use and when-not-to-use are both covered.

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

All Emero 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