Polyblog Multilingual Blog

List your blogs

list_blogs

Read-onlyIdempotent

Use this when someone asks which blogs they have in Polyblog, or a blog's id is needed. Returns each blog's id, name and custom domain, 25 per page by default with a cursor. Not for a blog's posts.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Blogs per page, from 1 to 100; defaults to 25
`cursor`	No	The nextCursor of the previous page; absent for the first page

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 / logoUrl

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

changedOutput schema / properties / items / items / required

Previous value: -[
-  "id",
-  "name",
-  "customDomain"
-]New value: +[
+  "id",
+  "name",
+  "customDomain",
+  "logoUrl"
+]

Changed3 schema fields changedSep 28, 2026

changedInput schema / properties / cursor / description

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

addedInput schema / properties / limit / description

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

addedOutput schema / properties / nextCursor / description

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

First observedSep 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds useful behavior beyond them: the page size default (25) and cursor-based pagination, plus what each result contains.

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 tight sentences: the primary use case leads, the exclusion follows. No filler and nothing redundant.

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 annotations carrying safety semantics and an output schema defining the return shape, the description covers everything an agent needs: purpose, trigger, pagination, and scope boundary.

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 both parameters (limit, cursor) are fully documented in the schema, so the baseline is 3. The description's mention of '25 per page by default with a cursor' restates schema information rather than adding syntax or format detail.

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+resource ('list your blogs') scoped to Polyblog, and further pins down the return payload (id, name, custom domain). It is clearly distinguishable from siblings like get_blog (single blog) and show_blog_overview.

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

Usage Guidelines4/5

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

Gives an explicit trigger ('when someone asks which blogs they have, or a blog's id is needed') and an explicit exclusion ('Not for a blog's posts'). It does not name the alternative tool for posts, but the when/when-not conditions are concrete.

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?