Flinty

Articles

list_articles

Read-onlyIdempotent

List articles. Optionally filter by status (draft, ready, scheduled, published, archived). Audience per article: google_clicks_90d (Search Console), reads_since_activation (audience pixel, humans, declared domains; since reads_since) and ai_robot_passes / ai_robots (AI robots, blogs served by Flinty only). A null audience field means NOT MEASURED, never zero. views_count is DEPRECATED: it only counts hits on the platform's own article page and misses every blog rendered on the client's site.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Max results (1-100, default 50)
`status`	No	Filter by article status

Output Schema

Name	Required	Description	Default
`articles`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 10, 2026

addedOutput schema / properties / articles / items / properties / ai_robot_passes
```
Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}
```

addedOutput schema / properties / articles / items / properties / ai_robots

Added value: +{
+  "additionalProperties": {
+    "type": "integer"
+  },
+  "type": "object"
+}

addedOutput schema / properties / articles / items / properties / google_clicks_90d
```
Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}
```
addedOutput schema / properties / articles / items / properties / reads_since
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / articles / items / properties / reads_since_activation
```
Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}
```

changedOutput schema / properties / articles / items / required

Previous value: -[
-  "id",
-  "title",
-  "slug",
-  "locale",
-  "status",
-  "refresh_status",
-  "published_at",
-  "scheduled_at",
-  "views_count",
-  "cluster_id",
-  "subject_id",
-  "created_at"
-]New value: +[
+  "id",
+  "title",
+  "slug",
+  "locale",
+  "status",
+  "refresh_status",
+  "published_at",
+  "scheduled_at",
+  "views_count",
+  "google_clicks_90d",
+  "reads_since_activation",
+  "reads_since",
+  "ai_robot_passes",
+  "ai_robots",
+  "cluster_id",
+  "subject_id",
+  "created_at"
+]

First observedNov 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely valuable interpretive behavior beyond that: a null audience field means NOT MEASURED rather than zero, and views_count is deprecated because it misses client-site blogs — both prevent real misinterpretation of results.

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?

The purpose and filter come first, then the metric glossary needed to read results correctly. The density of the audience-metric sentences is high but each clause carries meaning; no filler or restated title.

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?

With an output schema present, the description needn't explain return shape, and it compensates by explaining the semantics of the returned metric fields. Minor gaps remain — no statement about pagination, ordering, or what an omitted status returns — but nothing essential to a correct call is missing.

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?

Schema coverage is 100%, so baseline is 3, but the description goes further by enumerating the accepted status values (draft, ready, scheduled, published, archived) that the schema itself leaves as a bare string with no enum. It says nothing extra about limit beyond what the schema documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource ("List articles") and immediately states the filtering capability by status. It is distinguishable from get_article by the list/filter framing, though it never names the sibling explicitly to reinforce the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the agent learns it can optionally narrow by status, but there is no statement of when to prefer this over get_article or the other list_* siblings, and no mention of default behavior when status is omitted.

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

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