Skip to main content
Glama

List Marketing Studio presets

list_marketing_presets
Read-only

Presets for marketing-studio-2 and marketing-studio-flare. Pass one as preset_id to generate_assets along with 1 or 2 references (product first).

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_marketing_presets"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real value by disclosing the scope restriction (only presets for the two named studios) and the downstream reference ordering rule, but it says nothing about result volume, pagination, or whether the catalog is stable across calls.

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 short sentences with no filler; the resource scope is front-loaded and the follow-up sentence explains how to act on the output. Slightly indirect as an opening since it starts with a noun phrase rather than stating what the tool does.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only lister with no output schema, the definition should at least hint at what a preset record looks like and how cursor/search behave. It covers the ecosystem relationship to generate_assets well but leaves the listing behavior (result shape, paging) entirely undocumented.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both parameters (cursor and search), and the description mentions neither. The only parameter-like token, preset_id, belongs to generate_assets, not to this tool. An agent gets no help understanding that cursor paginates or that search filters by name.

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 names the concrete resource (presets) and scopes it to two specific studios, marketing-studio-2 and marketing-studio-flare, which lets an agent distinguish it from the other list_* siblings that return brands, formats, models, etc. It never states the verb 'list' or that it returns a collection, relying on the name and title for that, so it is clear but not fully self-contained.

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?

It gives explicit downstream guidance: pick a returned preset and pass it as preset_id to generate_assets, along with 1 or 2 references ordered product-first. That tells the agent the context in which this tool is useful, though it doesn't state when this tool should be skipped or what to do if no suitable preset exists.

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