API Ninjas

getInstitutionalHoldings

Read-only

Returns an institutional manager's full 13F portfolio for a quarter. Requires cik or manager_name. For every holder of a single stock use /institutionalownership.

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

Input Schema

Name	Required	Description
`cik`	No	Manager SEC Central Index Key (e.g. 1067983). Either cik or manager_name is required.
`sort`	No	Sort order: value (default), shares, percent_of_portfolio, or issuer_name.
`cusip`	No	Filter the portfolio to a single holding by CUSIP.
`limit`	No	Maximum results to return. Default 50, max 1000.
`offset`	No	Number of results to skip for pagination.
`period`	No	Quarter-end date (YYYY-MM-DD). Defaults to the latest quarter; free tier is limited to the most recent quarter.
`ticker`	No	Filter the portfolio to a single holding by ticker.
`group_by`	No	sector for a sector-allocation rollup. Business/Professional/annual plans only. Premium only.
`put_call`	No	put or call to filter option positions.
`max_value`	No	Maximum reported market value (USD).
`min_value`	No	Minimum reported market value (USD).
`change_type`	No	Comma-separated quarter-over-quarter filter: new, sold_out, increased, decreased, unchanged. Business/Professional/annual plans only. Premium only.
`manager_name`	No	Exact manager name (alternative to cik).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

A4.2/5.0

Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read. The description adds the quarter scope and the identifier requirement, but stays silent on tier gating (premium-only group_by/change_type, free-tier quarter limits) and pagination/return behavior, all of which matter for a 13-parameter query tool.

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, zero filler, front-loaded with the core behavior and followed immediately by the requirement and the routing alternative.

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 read-only, heavily parameterized tool whose schema documents all 13 parameters, the description covers identification and disambiguation adequately. It could note the premium/free-tier boundary for the gated filters, but that gap is partly covered by the schema itself.

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 including the premium-only and enum-constrained ones is already documented in the schema. The description only restates the cik/manager_name requirement, adding no syntax or format detail beyond the structured data.

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 with scope: 'Returns an institutional manager's full 13F portfolio for a quarter.' It also distinguishes itself from the sibling route /institutionalownership (the getInstitutionalOwnership tool) by describing the inverse query direction.

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 constraint ('Requires `cik` or `manager_name`') and routes the agent to the alternative for the opposite case ('For every holder of a single stock use /institutionalownership'). Nothing is left to inference.

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

All API Ninjas tools Inspect

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

Need Help?