coinrebate

get_latest_news

Read-onlyIdempotent

Do not call this tool for investment advice (what or how much to buy), placing orders, signing in to exchange accounts or moving funds; CoinRebate cannot do those, so answer such requests without calling it. Get CoinRebate's most recently published English-language articles (market analysis, guides and news), newest first: up to five by default, at most 20. Returns each article's title, publication date and link, and says so when the newest English-language article is more than three days old. Use it only when the user asks what CoinRebate has published.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of English-language articles to return (1-20; up to 5 by default)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`stale`	Yes
`articles`	Yes
`language`	Yes
`news_url`	Yes
`latest_date`	Yes
`latest_age_days`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedOct 7, 2026

changedInput schema / properties / limit / description

Previous value: -"Number of articles to return (1-20, default 5)"New value: +"Maximum number of English-language articles to return (1-20; up to 5 by default)"

addedOutput schema / properties / articles / items / properties / date
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / articles / items / properties / type

Added value: +{
+  "enum": [
+    "guide",
+    "news"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / articles / items / required

Previous value: -[
-  "slug",
-  "title",
-  "url"
-]New value: +[
+  "slug",
+  "title",
+  "url",
+  "date",
+  "type"
+]

addedOutput schema / properties / language

Added value: +{
+  "const": "en",
+  "type": "string"
+}

addedOutput schema / properties / latest_age_days

Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / latest_date

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / stale
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / required

Previous value: -[
-  "articles",
-  "news_url"
-]New value: +[
+  "articles",
+  "news_url",
+  "language",
+  "latest_date",
+  "latest_age_days",
+  "stale"
+]

First observedSep 18, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare the operation is read-only, idempotent, and non-destructive. The description goes further, disclosing that results are newest-first, capped at 5 by default and 20 max, that each item carries title/date/link, and that it signals when the newest article is over three days old – genuinely useful behavioral context not present in annotations.

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?

Dense but front-loaded: the exclusions and routing rule come first, then the return semantics. Every clause carries information, though the paragraph runs long enough that the positive purpose is somewhat buried after the negative guidance.

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 read-only annotations, a fully documented parameter, and an existing output schema, the remaining burden is scope and routing – both fully addressed. An agent has everything needed to decide to call it and how to interpret the response, including the staleness signal.

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% and the single 'limit' parameter is fully documented in the schema (default 5, min 1, max 20). The description's 'up to five by default, at most 20' merely restates the schema, so it earns the baseline rather than extra credit.

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: 'Get CoinRebate's most recently published English-language articles (market analysis, guides and news)'. It clearly distinguishes itself from sibling tools like compare_fees, get_exchange_fees, and search_guides by scoping to newly published content.

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 enumerates when NOT to use it (investment advice, placing orders, signing in, moving funds) and gives the sole positive condition: 'Use it only when the user asks what CoinRebate has published.' Names the routing rule and the fallback behavior for out-of-scope requests.

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

All coinrebate 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.