Polyblog Multilingual Blog

Find blog posts

search_articles

Read-onlyIdempotent

Use this when someone asks to see their blog posts, drafts or published articles, optionally for one blog, language or slug. Returns id, title, language, slug and published state, most recently edited first, 25 per page by default with a cursor. It filters by those fields and does not search the text. Not for reading a post.

Input Schema

TableJSON Schema

Name	Required	Description
`slug`	No	Only the post with this exact slug
`limit`	No	Posts per page, from 1 to 100; defaults to 25
`blogId`	No	Only posts in this blog
`cursor`	No	The nextCursor of the previous page with the same filters; absent for the first page
`locale`	No	Only posts in this language, an ISO 639-1 code such as en or it
`published`	No	"true" for published posts only, "false" for drafts only; omit for both

Output Schema

TableJSON Schema

Name	Required	Description
`items`	Yes
`hasMore`	Yes
`nextCursor`	Yes	Cursor for the next page; null on the last page

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 1, 2026

addedOutput schema / properties / items / items / properties / coverUrl

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

changedOutput schema / properties / items / items / required

Previous value: -[
-  "id",
-  "title",
-  "locale",
-  "slug",
-  "published"
-]New value: +[
+  "id",
+  "title",
+  "locale",
+  "slug",
+  "published",
+  "coverUrl"
+]

Changed7 schema fields changedSep 28, 2026

changedInput schema / properties / blogId / description

Previous value: -"Filter to a specific blog"New value: +"Only posts in this blog"

changedInput schema / properties / cursor / description

Previous value: -"Opaque pagination cursor from a previous call"New value: +"The nextCursor of the previous page with the same filters; absent for the first page"

addedInput schema / properties / limit / description

Added value: +"Posts per page, from 1 to 100; defaults to 25"

changedInput schema / properties / locale / description

Previous value: -"ISO 639-1 locale code, e.g. \"en\", \"it\""New value: +"Only posts in this language, an ISO 639-1 code such as en or it"

changedInput schema / properties / published / description

Previous value: -"Filter by published state"New value: +"\"true\" for published posts only, \"false\" for drafts only; omit for both"

changedInput schema / properties / slug / description

Previous value: -"Exact slug match"New value: +"Only the post with this exact slug"

addedOutput schema / properties / nextCursor / description

Added value: +"Cursor for the next page; null on the last page"

First observedSep 11, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent and closed-world, so the safety profile is covered; the description adds genuinely new behavior: return fields, sort order ('most recently edited first'), default page size of 25 with cursor pagination, and the key limitation that it filters by fields rather than searching text.

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?

Three sentences, zero padding, front-loaded with the trigger condition, then return/pagination behavior, then the exclusion. Every clause carries information.

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 an output schema present, the description need not enumerate return values, yet it still previews the key fields and result ordering. Together with the annotations and full schema coverage, an agent has everything needed to call and interpret this correctly.

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 the baseline is 3, but the description adds semantics beyond the schema: it explains that filtering is field-based and not full-text, restates the 25-per-page default with a cursor, and groups the filterable fields (blog, language, slug) so the agent understands the filter model.

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 (search/filter) and resource (blog posts) with scope: drafts or published articles, optionally narrowed by blog, language or slug. It clearly distinguishes itself from get_article by naming the exclusion 'Not for reading a post.'

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?

Opens with an explicit trigger ('Use this when someone asks to see their blog posts, drafts or published articles') and closes with an explicit non-use case ('Not for reading a post'), routing the agent to get_article instead.

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

All Polyblog Multilingual Blog 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?