Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_get_account_activity_logs

Retrieve account activity logs to monitor user actions and system events for auditing and troubleshooting purposes.

Instructions

Retrieve activity logs for the account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
per_pageNo

Implementation Reference

  • The handler function for 'pressable_get_account_activity_logs' which calls the API to retrieve account activity logs.
    handler: async (args) => {
        return await api.get('/account/activity_logs', args);
    }
  • tools/account.js:12-25 (registration)
    The tool definition and registration for 'pressable_get_account_activity_logs'.
    {
        name: 'pressable_get_account_activity_logs',
        description: 'Retrieve activity logs for the account.',
        inputSchema: {
            type: 'object',
            properties: {
                page: { type: 'integer' },
                per_page: { type: 'integer' }
            }
        },
        handler: async (args) => {
            return await api.get('/account/activity_logs', args);
        }
    },
Behavior2/5

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

No annotations are provided, yet the description discloses minimal behavioral context. It does not state whether this is read-only, what time range the logs cover, pagination limits, or the format/structure of the returned data. 'Retrieve' implies safety but does not explicitly confirm it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is appropriately brief but underweight for the tool's complexity. It is front-loaded with the action, but the brevity wastes the opportunity to clarify scope and distinguish from siblings.

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?

Given the ambiguous relationship with the sibling actions tool and the undocumented pagination parameters, the description is incomplete. Without an output schema, the description should ideally characterize the log content, which it does not.

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

Parameters2/5

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

With 0% schema description coverage, the description must compensate but mentions nothing about the page and per_page parameters. No information about default values, maximum limits, or pagination semantics is provided.

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 clear verb (Retrieve) and resource (activity logs for the account), but fails to distinguish from the nearly identical sibling tool pressable_get_account_activity_log_actions. Without clarification on scope differences, agents cannot confidently select between them.

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 the sibling get_account_activity_log_actions, nor any pagination guidance for the page/per_page parameters. No prerequisites or filtering guidance is mentioned.

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