Skip to main content
Glama
Sign In

AskEditor

by com.askeditor
OverviewDiscussionsAdmin

List motion graphics

list_assets
Read-onlyIdempotent

[read] List the motion graphics this project can place — its own and the brand's — with status, format, length, and whether each has code yet. Use before rewriting, rendering, scoring or deleting a graphic. Not for photos, video or audio files (use list_media). Returns assets [{id, title, kind, format, status, hasCode, durationMs}], 100 a page, total, next_offset. Related: write_asset, render_asset, delete_asset.

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": {
      "project_id": "<project_id>"
    },
    "name": "list_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 100, max 200.
offsetNoStart (default 0).
searchNoIn the title.
project_idYesThe AskEditor project this acts on (from list_projects).

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 and non-destructive, so the safety profile is covered. The description adds value annotations don't: the return shape, page size of 100, a total count and next_offset for pagination, plus related mutation tools. It does not, however, mention ordering or whether results are filtered by status.

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 tight sentences: purpose and scope first, then usage routing, then return shape and siblings. No filler, and the [read] tag front-loads the operation class.

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, so the description carries the return contract itself and does so precisely (field list, page size, total, next_offset). Combined with a fully documented 4-parameter schema and rich annotations, an agent has everything needed to call and interpret this tool.

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 the schema already documents limit, offset, search and project_id, making 3 the baseline. The description only echoes page size ("100 a page") and never mentions the search-by-title parameter, adding little beyond the schema.

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 ("List the motion graphics this project can place") and pins the scope (own + brand's), then enumerates the fields returned. It explicitly distinguishes itself from list_media, which handles other media types, so an agent can route without opening a schema.

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?

Gives concrete timing ("Use before rewriting, rendering, scoring or deleting a graphic") and an explicit exclusion with the correct alternative ("Not for photos, video or audio files (use list_media)"). Both when-to-use and when-not-to-use are present.

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

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