Skip to main content
Glama

List Filings

ListFilings
Read-only

List stored SEC filings and earnings-call transcripts newest first. Omit ticker for a market-wide feed or provide one ticker for a company-specific list. Returns company identity, document IDs, types, filing and reporting dates, SEC item numbers, line counts, EDGAR accession numbers and acceptance times (UTC; blank for filings stored before October 2026), and page totals. Supports date, document-type, and exact SEC item-number filters. Hidden document types remain excluded unless explicitly requested. When the deployment summarizes documents, each row adds a short summary of what the document says, and when it has a public document viewer, each row adds the filing's page URL to share with the user. Pass a returned ID to SearchDocument or ReadDocumentLines.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for pagination (default: 1)
tickerNoOptional company ticker symbol (e.g., AAPL, MSFT); a listing outside the US is MIC:TICKER (e.g. XPAR:AIR), whose list includes its ESEF reports. Omit for all companies.
endDateNoOptional end date filter in YYYY-MM-DD format
maxItemsNoMaximum number of documents per page (default: 10)
startDateNoOptional start date filter in YYYY-MM-DD format
itemNumberNoOptional exact SEC current-report item number, e.g. 2.02, 5.02, or 1.01.
documentTypeNoDocument type filter: a registered value such as 'TenK', 'TenQa', 'EightK', 'TwentyF', 'Def14A', 'Defa14A', 'SThree' or 'TenderOfferThirdParty', or its SEC form name ('10-K', '20-F/A', 'DEFA14A', 'S-3ASR', 'SC TO-T', 'NT 10-Q'), plus deployment-registered types such as EarningsCallTranscript. An unrecognized value returns an error listing every accepted value.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / ticker / description
      Previous value: -"Optional company ticker symbol (e.g., AAPL, MSFT). Omit for all companies."New value: +"Optional company ticker symbol (e.g., AAPL, MSFT); a listing outside the US is MIC:TICKER (e.g. XPAR:AIR), whose list includes its ESEF reports. Omit for all companies."
  2. Changed1 schema field changed
    • changedInput schema / properties / documentType / description
      Previous value: -"Document type filter. Accepts a registered type value — 'TenK', 'TenQ', 'EightK', 'TenKa', 'TenQa', 'EightKa', 'TwentyF', 'SixK', 'FortyF', 'TwentyFa', 'SixKa', or 'FortyFa' — or its display name (e.g. '10-K', '20-F/A'), plus any deployment-registered type, such as EarningsCallTranscript (display name: Earnings Call) for earnings-call transcripts where available. An unrecognized value returns an error listing every accepted value."New value: +"Document type filter: a registered value such as 'TenK', 'TenQa', 'EightK', 'TwentyF', 'Def14A', 'Defa14A', 'SThree' or 'TenderOfferThirdParty', or its SEC form name ('10-K', '20-F/A', 'DEFA14A', 'S-3ASR', 'SC TO-T', 'NT 10-Q'), plus deployment-registered types such as EarningsCallTranscript. An unrecognized value returns an error listing every accepted value."
  3. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld/destructive annotations: it discloses default exclusion of hidden document types, the newest-first ordering, that acceptance times are UTC and blank for pre-October-2026 filings, and that summary text and page URLs appear only in deployments configured with those features. These conditional behaviors are exactly what an agent cannot infer from the structured fields.

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?

Front-loads the core action and scope before the long return-field enumeration, and every sentence carries information. The return-value sentence is a run-on enumeration that could be tightened, but nothing is genuinely wasteful given there is no output schema.

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?

With no output schema and seven optional parameters, the description carries the full burden and does so: it enumerates returned fields, explains ordering, conditional enrichment, and hidden-type exclusion, and tells the agent what to do with a returned ID. Nothing essential for correct invocation is missing.

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 coverage is 100%, so the schema already documents every parameter including the ticker MIC:TICKER form, date formats, and accepted document-type values. The description adds only marginal semantics over that baseline (ticker omission means market-wide, item-number matching is exact), so the standard baseline of 3 applies.

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 stored SEC filings and earnings-call transcripts') plus the ordering ('newest first') and scope control (market-wide vs one ticker). This is clearly distinguishable from the sibling read/search tools it names at the end.

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?

Gives concrete selection criteria: omit ticker for a market-wide feed, supply one ticker for a company list, and use hidden types only when explicitly requested. It also routes the agent forward ('Pass a returned ID to SearchDocument or ReadDocumentLines'), though it never states when to skip listing entirely and go straight to SearchDocument for full-text queries.

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.