Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

pressable_list_sites

Retrieve and filter your WordPress sites from your Pressable account, with options for pagination and tag-based organization.

Instructions

Get a list of sites belonging to your account. Sites can be filtered by tag name or paginated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paginateNoRequest a paginated response
per_pageNoAmount of sites returned in a response
pageNoPage of the response
tagNoFilter sites by tag name

Implementation Reference

  • tools/sites.js:16-18 (handler)
    The handler function that executes the logic for 'pressable_list_sites' by calling the sites API.
    handler: async (args) => {
    return await api.get('/sites', args);
}
  • tools/sites.js:7-15 (schema)
    The input schema definition for 'pressable_list_sites', defining the expected parameters.
    inputSchema: {
    type: 'object',
    properties: {
        paginate: { type: 'boolean', description: 'Request a paginated response' },
        per_page: { type: 'integer', description: 'Amount of sites returned in a response' },
        page: { type: 'integer', description: 'Page of the response' },
        tag: { type: 'string', description: 'Filter sites by tag name' }
    }
},

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the basic action and mentions filtering/pagination, but does not disclose authentication requirements, default pagination behavior, response format, or any side effects. This is minimal and leaves many behavioral aspects to the agent's speculation.

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?

The description is exactly two sentences, front-loading the primary purpose and then adding the key option (filter/paginate). Every word earns its place, with no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 4 parameters, no annotations, and no output schema, the description is adequate but not complete. It covers the core purpose and introduces pagination, but does not explain return values or response structure, which would be helpful since there is no output schema. It remains minimally viable but with clear gaps in context.

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 100%, so the parameters are already well-documented with descriptions for tag, page, paginate, and per_page. The description reiterates that sites can be filtered by tag or paginated, but adds no new meaning beyond the schema. This aligns with the baseline of 3 for full schema coverage.

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?

The description uses a specific verb ('Get') with a clear resource ('a list of sites') and scope ('belonging to your account'), distinguishing it from sibling tools like pressable_get_site (singular) and pressable_list_site_domains (domains). It accurately captures the tool's function as a listing operation.

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?

The description implies usage for listing sites with optional tag filtering and pagination, but does not explicitly state when to prefer this over alternatives like pressable_get_site for a single site. There are no exclusions or when-not-to-use scenarios, leaving the context partially implied.

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

Deploy Server

Other Tools