Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaRelated ServersScoreDiscussions
JavaScript

pressable_list_themes

Retrieve available WordPress themes for a specific Pressable site to manage site appearance and functionality.

Instructions

Get a list of themes for a specific site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • tools/content.js:39-41 (handler)
    The handler for pressable_list_themes that calls the API to get themes for a site.
    handler: async (args) => {
    return await api.get(`/sites/${args.id}/themes`);
}
  • tools/content.js:34-38 (schema)
    Input schema for pressable_list_themes tool.
    inputSchema: {
    type: 'object',
    properties: { id: { type: 'string' } },
    required: ['id']
},
  • tools/content.js:31-42 (registration)
    Registration of the pressable_list_themes tool within the contentTools array.
    {
    name: 'pressable_list_themes',
    description: 'Get a list of themes for a specific site.',
    inputSchema: {
        type: 'object',
        properties: { id: { type: 'string' } },
        required: ['id']
    },
    handler: async (args) => {
        return await api.get(`/sites/${args.id}/themes`);
    }
},

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. Fails to disclose if this is read-only, what the response format includes (active vs inactive themes, theme attributes), error behavior, or pagination. Minimal safety/behavioral context.

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?

Single sentence with no waste. Appropriately front-loaded with the action. However, given the lack of schema descriptions and annotations, extreme brevity harms completeness.

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

Completeness2/5

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

With zero schema descriptions, no output schema, and no annotations, the description must do heavy lifting. It fails to specify what the 'id' parameter represents (site ID vs other ID) or describe return values, leaving significant gaps in agent understanding.

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?

With 0% schema coverage, the description must compensate. The phrase 'for a specific site' implicitly signals that the 'id' parameter refers to the site identifier, adding critical semantic meaning absent from the schema. However, it doesn't explicitly document the parameter or its format.

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?

States a clear verb ('Get') and resource ('list of themes') with scope ('for a specific site'). Distinguishes from sibling tools like pressable_list_plugins and pressable_list_sites by specifying the correct resource type, though it doesn't explicitly contrast with them.

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?

Implies when to use (when you need themes for a site) but lacks explicit when-not guidance or alternatives. No mention of prerequisites like needing a valid site ID or how this compares to pressable_get_site.

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