Skip to main content
Glama

The Marketing Vault

List saved outputs

list_saved_outputs
Read-onlyIdempotent

Lists the user's saved marketing outputs from their Marketing Vault library, newest first. Optionally includes the full text of each output.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows (default 20).
searchNoOptional keyword filter on title.
full_textNoInclude the full output body instead of a preview.
business_profile_idNoOptional business filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds a genuine behavioral detail the annotations lack — results are ordered newest first — but says nothing about pagination, total counts, or result shape.

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 sentences, tightly written, with the core scope and ordering front-loaded. There is negligible waste, though it is arguably thin rather than maximally informative.

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 a simple, zero-required-parameter, read-only list tool with full schema coverage and no output schema, the definition covers what the tool returns at a high level (saved outputs, newest first, preview vs. full body). Only pagination/return-shape detail is missing, which is minor here.

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 every parameter (limit, search, full_text, business_profile_id) is already documented in the schema. The description only echoes the full_text behavior and adds no syntax, defaults, or edge-case details beyond it, so the baseline 3 applies.

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 ("Lists the user's saved marketing outputs from their Marketing Vault library") plus the sort order, which lets an agent distinguish this read tool from the write-side sibling save_output. It never names an alternative explicitly, so it falls just short of a 5.

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?

Usage is implied by the phrasing: browse saved outputs, optionally with full text. There is no explicit when-to-use/when-not-to-use statement and no pointer to an alternative retrieval tool (e.g., a search or get-by-id tool) if one 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