Skip to main content
Glama
Sign In

CueFrame

by ai.cueframe
OverviewDiscussionsAdmin

List Briefs

list_briefs
Read-onlyIdempotent

List briefs. DEFAULT shows human-authored briefs only; kind:"clip" shows the machine-minted clip briefs (suggest_briefs output), kind:"all" shows everything. Each carries its quote.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_briefs"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoWhich briefs to list. `authored` (default) = human-authored only; `clip` = the machine-minted clip briefs from suggest_briefs; `all` = both.
afterNoOpaque cursor from the previous page's `pagination.nextCursor`. Forward-only.
limitNoPage size (1..100), default 20. Out-of-range or unparseable clamps into the range.
projectIdNoScope to one project. Omit for every brief in the org.

Output Schema

NameRequiredDescriptionDefault
dataNo
paginationNoCursor pagination metadata.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent read. The description adds a genuinely non-obvious behavioral trait: the DEFAULT result set is filtered to human-authored briefs only, so an agent won't silently miss clip briefs. It also notes "Each carries its quote," hinting at payload content. Leaving out pagination behavior keeps it just short of a 5.

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?

Two dense sentences with the default behavior front-loaded before the alternatives, which is the correct ordering. "Each carries its quote" is slightly opaque out of context, costing a point, but nothing is padded.

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 an output schema present, return shape needs no explanation, and annotations cover the safety profile. The description supplies the critical default-filtering caveat; the only real gap is any mention of cursor-based pagination beyond what the schema states.

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 all four parameters including `after`, `limit`, and `projectId`. The description only restates the `kind` semantics (adding the mild extra context that clips originate from suggest_briefs) and says nothing about the other three parameters, so baseline 3 is right.

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?

States a specific verb and resource ("List briefs") and immediately characterizes the three scopes the result set can take, which is the main thing separating this from a plain enumeration. It does not differentiate itself from close siblings like editorial_list_briefs or get_brief, so an agent must still reason about which brief-listing tool to pick.

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

Usage Guidelines3/5

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

The description explains how the `kind` values change results, which implies when to reach for each mode, but it never states when to use this tool instead of get_brief, editorial_list_briefs, or create_brief. Usage is inferable rather than explicit.

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

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