TipRanks

get_buybacks

Read-onlyIdempotent

Returns share-buyback / stock-repurchase activity in one of two modes:

- CROSS-MARKET (no ticker): latest reported buybacks across all companies,
  sorted by dollar amount spent (largest first). Use for 'biggest buybacks',
  'top repurchase companies'. A single company may appear multiple times for
  different fiscal quarters.
- PER-TICKER (ticker provided): historical quarterly buyback series for one
  ticker. Use for 'AAPL buyback history', 'MSFT repurchase trend'.

Args:
    ticker: Optional. If provided, returns the per-ticker historical series.
            If empty, returns the cross-market list.
    limit: Cross-market mode only — max rows (default: 25, max: 100).
    page: Cross-market mode only — page number, 1-based (default: 1).

Returns:
    Cross-market mode: { totalCount, data: [{ ticker, companyName,
                         fiscalPeriodEndDate, stockEarningsDate, eps,
                         marketCapUSD, totalValueSpentToRepurchaseShares,
                         epsCurrencyTypeCode }] }.
    Per-ticker mode: quarterly time series, chart-ready as a bar or
        line plot of buyback spend over time —
        [{ date, marketCapEndFiscalPeriod,
           totalValueSpentToRepurchaseShares,
           ratio (decimal — buyback / market cap) }, ...].

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No
`limit`	No
`ticker`	No	Optional. If provided, returns the per-ticker historical buyback series; if omitted, returns the cross-market list.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 17, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_buybacksOutput",
-  "type": "object"
-}New value: +null

First observedJul 21, 2026

TDQS

A4.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, which the description does not contradict. Adds useful behavioral context: cross-market results are sorted by dollar amount, a company may appear multiple times for different fiscal quarters, and per-ticker returns are chart-ready time series.

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?

The description is well-structured with clear sections for modes, arguments, and returns. Every sentence adds value, and the formatting makes it easy to parse.

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?

Since there is no output schema, the description provides comprehensive return field details for both modes, including example field names and the chart-ready nature of per-ticker data. It covers all parameters and operational modes thoroughly.

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

Parameters5/5

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

Description fully explains each parameter beyond the schema. It clarifies that limit and page are cross-market-only with defaults and max, and that ticker determines mode. This compensates for the sparse 33% schema description coverage.

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 'Returns share-buyback / stock-repurchase activity' with two distinct modes, making the tool's purpose clear. It clearly distinguishes from sibling get_* tools by focusing specifically on buyback/repurchase data.

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 provides example queries for each mode: 'biggest buybacks', 'top repurchase companies' for cross-market, and 'AAPL buyback history', 'MSFT repurchase trend' for per-ticker. Also specifies when to omit versus provide ticker, giving clear directional guidance.

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

All TipRanks 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?