Skip to main content
Glama

brochure_list

Read-onlyIdempotent

FREE, no key: the public directory of brochures. tab trending (views, follows and copies the deck measures, over range 1d, 7d or 30d), new, or proof (the reader gate's verdict, then receipts, then forward days; never by return); filters kind, market, venue, tag, q. mine true (with your key) lists your own pages in every status.

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": "brochure_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNowords in the title, tagline or tags
tabNotrending (default), new or proof
tagNoonly pages with this tag
kindNoonly this kind
mineNoyour own pages, every status (needs your key)
rangeNotrending's window
venueNoonly pages on this venue (its id)
marketNoonly pages on this market

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the read-only annotations, the description adds useful behavioral context: public access requires no key, mine=true requires a key and returns pages in every status, and trending measures views/follows/copies over a selected range. It does not describe pagination or result size limits, but the annotations already establish the safe read-only profile.

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?

The definition is front-loaded with the essential access fact (FREE, no key) and then covers tabs and filters compactly. Some phrasing is cryptic, especially the proof-tab explanation, but there is little wasted text overall.

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?

For an eight-parameter, optional-argument list tool with no output schema, the description covers the important access model, modes, ranges, and filters. It could add more on pagination or return shape, but the annotations and schema carry enough of the remaining burden that the description is substantially complete.

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, but the description adds meaning beyond the schema: trending is tied to views, follows, and copies over range 1d/7d/30d, proof is described as an ordered reader-gate verdict sequence, and mine is tied to the user's key and all statuses. Some filter parameters such as venue and market remain only schema-defined, but the key modes are meaningfully explained.

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?

The description clearly identifies the tool as the public directory/listing of brochures, with modes for trending, new, proof, and a mine=true own-pages variant. It is clear what resource is being listed, though it does not explicitly contrast itself with sibling tools such as brochure_get or brochure_draft.

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?

It explains the available listing modes and notes that the public directory needs no key while mine=true requires a key. However, it gives no explicit guidance on when to use this tool instead of siblings like brochure_get or how to choose among the tabs for a given task.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources