Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_get_sftp_users

Retrieve SFTP user accounts for a WordPress site to manage file access and permissions through the Pressable API.

Instructions

Get a list of SFTP users for a specific site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • The handler for the 'pressable_get_sftp_users' tool, which makes an API request to fetch SFTP users for a site.
    handler: async (args) => {
        return await api.get(`/sites/${args.id}/sftp-users`);
    }
  • tools/server.js:4-15 (registration)
    The registration of the 'pressable_get_sftp_users' tool definition, including its schema and handler.
    {
        name: 'pressable_get_sftp_users',
        description: 'Get a list of SFTP users for a specific site.',
        inputSchema: {
            type: 'object',
            properties: { id: { type: 'string' } },
            required: ['id']
        },
        handler: async (args) => {
            return await api.get(`/sites/${args.id}/sftp-users`);
        }
    },
Behavior2/5

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

No annotations provided, so description carries full burden. 'Get' implies read-only but doesn't confirm safety, auth requirements, rate limits, or return format. No disclosure of what happens if the site ID is invalid.

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, front-loaded with action. Efficient at 9 words, though brevity leaves gaps given the complete lack of annotations and schema descriptions.

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?

Minimum viable for a simple list retrieval with one parameter. Lacks output schema explanation (not required) but given 0% schema coverage and no annotations, should explicitly map the 'id' parameter to 'site_id'.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema coverage (no description for 'id'), the phrase 'for a specific site' provides critical semantic context implying the 'id' parameter refers to the Site ID. However, it doesn't explicitly confirm 'id = site_id' or describe the expected ID 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?

Clear verb ('Get') and resource ('SFTP users') with scope ('for a specific site'). Distinguishes from sibling 'pressable_reset_sftp_user_password' (list vs reset) and 'pressable_list_wp_users' (SFTP vs WordPress users) implicitly through specific resource naming.

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?

No explicit guidance on when to use vs alternatives (e.g., when to use this vs 'pressable_reset_sftp_user_password'), no prerequisites mentioned, and no error conditions described.

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