Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaRelated ServersScoreDiscussions
JavaScript

pressable_enable_site

Activate a WordPress site on Pressable by providing its ID or name to restore functionality and access.

Instructions

Enable a specific site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe site ID or name

Implementation Reference

  • tools/sites.js:89-91 (handler)
    The handler for the 'pressable_enable_site' tool that calls the API to enable the site.
    handler: async (args) => {
    return await api.post(`/sites/${args.id}/enable`);
}
  • tools/sites.js:82-88 (schema)
    The input schema definition for 'pressable_enable_site'.
    inputSchema: {
    type: 'object',
    properties: {
        id: { type: 'string', description: 'The site ID or name' }
    },
    required: ['id']
},
  • tools/sites.js:80-81 (registration)
    The registration of the 'pressable_enable_site' tool within the tools list.
    name: 'pressable_enable_site',
description: 'Enable a specific site.',

Tool Definition Quality

C2.6/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 but fails to deliver. It does not indicate whether the change is reversible, what happens to site accessibility, or whether this operation is destructive or safe. The agent learns only that a state change occurs.

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?

The description is extremely brief at four words, with no redundancy or filler. However, this conciseness crosses into under-specification, as the single sentence omits critical behavioral and contextual details necessary for confident tool selection.

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?

For a state-changing tool with no output schema and no annotations, the description is inadequate. It fails to explain the 'enabled' state semantics, side effects, or success indicators. Even with only one parameter, the ambiguity surrounding the 'enable' action leaves significant gaps.

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?

The input schema has 100% coverage with the 'id' parameter documented as 'The site ID or name'. The description adds no additional context about parameter format, valid ID patterns, or where to obtain site IDs, warranting the baseline score for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Enable') and resource ('site'), but remains vague about what 'enable' entails in the Pressable context (e.g., reactivating a suspended site vs. taking it out of maintenance mode). It does not distinguish from siblings like 'create_site' or clarify the relationship to 'disable_site'.

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?

The description provides no guidance on when to use this tool versus alternatives such as 'create_site', 'restore_site', or 'disable_site'. There is no mention of prerequisites (e.g., the site must exist and be disabled) or explicit pairing with its counterpart 'disable_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