Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaRelated ServersScoreDiscussions
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' }
    }
},

Tool Definition Quality

B3.4/5.0
Behavior3/5

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

No annotations provided, so description carries full disclosure burden. Mentions pagination and tag filtering behaviors explicitly, which is helpful. However, fails to clarify safety properties (read-only vs destructive), rate limits, or what the response structure 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 efficient sentences with zero waste. Front-loaded with primary purpose ('Get a list of sites'), followed by capability modifiers ('filtered by tag name or paginated'). No redundant phrases or tautology.

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?

Appropriately complete for a straightforward list operation with 4 optional parameters and 100% schema coverage. Lacks output description but no output schema exists to require it. Minor gap: could benefit from safety classification given zero annotations.

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 has 100% description coverage, establishing baseline 3. Description mentions 'filtered by tag name or paginated' which aligns with parameters but adds no semantic detail beyond schema descriptions (e.g., no guidance on per_page limits or pagination logic).

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?

Clear verb ('Get') and resource ('list of sites') with scope ('belonging to your account'). However, it fails to explicitly distinguish from sibling 'pressable_get_site' which retrieves a specific site versus this tool which enumerates multiple sites.

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

Usage Guidelines2/5

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

Provides no guidance on when to use this tool versus alternatives like 'pressable_get_site'. Missing prerequisites (e.g., authentication requirements) and exclusion criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PCWProps/pressable-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server