Skip to main content
Glama
Sign In

PixelGlass

by co.pixelglass
OverviewDiscussionsAdmin

List posts

list_posts
Read-onlyDestructive

On one site of the account, named in site. The publication's posts and pages, newest first, fifty a page: id, title, kind, status, language, slug and a preview link. Filter by status, kind, language, tag slug, author slug, collection or a search string over the title and text. Use the id with get_post and the writing tools.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>"
    },
    "name": "list_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoWords to look for in titles and text
tagNoA tag's slug
kindNo
pageNo1 by default
siteYesThe site to work on, as list_sites names it
authorNoA staff member's slug
statusNo
languageNoA BCP 47 tag the publication publishes in
collectionNoA collection's id, slug or name: its pages alone (get_collection gives them as a tree)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare this a read operation, and the description adds behavior the annotations cannot: newest-first ordering, a fifty-per-page page size, and the exact field set returned. It does not state whether a next page exists or how to detect the end of the result set, which is the main remaining gap. Nothing here contradicts the 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?

Three short sentences, front-loaded with scope and ordering, with zero filler. The telegraphic fragment style costs a little readability but nothing is wasted.

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 nine parameters and no output schema, the description does the right work by enumerating returned fields and the page size, which substitutes for a return-value section. It stops short of describing pagination termination or result caps, the one thing an agent paging through results still needs.

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 coverage is 78%, so the schema already documents most parameters and the description largely restates them (status, kind, language, tag slug, author slug, collection, search string). It does add one genuinely new fact by tying 'page' to a page size of fifty, but the individual filter semantics come from the schema rather than the description.

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 names the resource ('posts and pages'), the scope ('one site of the account, named in site') and the returned fields, which is enough to tell it apart from get_post and list_site_pages. It is written in clipped fragments ('On one site of the account, named in site.') so there is no explicit verb, but the listing intent is unmistakable.

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?

It routes the agent downstream ('Use the id with get_post and the writing tools') and names a sibling for the tree view of collection pages ('get_collection gives them as a tree'). What is missing is an explicit statement of when to prefer this over list_site_pages or list_tags, and there are no exclusions.

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

All PixelGlass toolsInspect
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