Skip to main content
Glama
Sign In

Storefinch

by com.storefinch
OverviewDiscussionsAdmin

List recent exports

list_exports
Read-onlyIdempotent

List exports made with this API key in the last 7 days, newest first, each with its filters, row count and a fresh download link valid 24 hours. Use it to get a file again after its link expired instead of re-running export_leads: re-downloading is free, while a new export uses quota. Free: it doesn't count against the quota.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
exportsYesNewest first, from the last 7 days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses concrete behavior an agent cannot infer: the 7-day lookback window, newest-first ordering, link lifetime of 24 hours, and that calls do not consume quota. These are exactly the facts needed to decide whether a call is safe and worthwhile.

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?

Two sentences, both front-loaded with the operative information: what is returned first, then when to prefer it over the alternative. No redundant restatement of the title or name.

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?

For a zero-parameter read tool with an output schema and full annotation coverage, nothing material is missing. The freshness window, ordering, link expiry, and quota cost are all stated, so an agent can call it without further discovery.

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?

The tool takes zero parameters, so the schema carries no semantics to supplement and the baseline is high. The description does describe what each result contains (filters, row count, download link), which is useful context even if a dedicated output schema already exists.

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 exports made with this API key') plus precise scope: last 7 days, newest first, with filters, row count and a 24-hour download link. That level of detail makes it trivially distinguishable from the sibling export_leads, which creates new exports.

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?

Explicitly names the alternative and the condition that selects this tool: use it to re-download a file after its link expired instead of re-running export_leads. It also gives the deciding rationale — re-downloads are free while a new export consumes quota.

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

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