Skip to main content
Glama
Sign In
Shopmonkey MCP Server

Shopmonkey MCP Server

by AbbottDevelopments
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_webhooks

List all Shopmonkey webhooks with pagination to track and manage event subscriptions.

Instructions

List all registered webhooks in Shopmonkey.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_webhooks"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNoNumber of records to skip for pagination (default: 0)
limitNoMaximum number of results to return (default: 25)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.1

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of disclosing side effects. It only says 'List', which implies a read-only operation, but does not explicitly state that no modifications occur or that authentication is required. The absence of any side-effect disclosure is a minor gap.

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?

The description is a single, concise sentence that immediately conveys the tool's purpose. It is front-loaded with the verb and resource, with no fluff or redundant information.

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?

For a simple list operation, the description is complete enough. It does not require an output schema explanation, and the pagination parameters are already documented. It could mention whether the list is ordered or includes archived webhooks, but such details are beyond the minimal context needed to invoke the tool successfully.

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 schema already provides descriptions for both skip and limit parameters (100% coverage). The description adds no additional meaning about how these parameters affect the listing, such as sorting or default pagination behavior, so it neither enhances nor detracts from the schema.

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

Purpose5/5

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

The description clearly states the action (list) and resource (all registered webhooks in Shopmonkey), and naturally distinguishes itself from the sibling get_webhook, which retrieves a single webhook.

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?

While the description implies its use for retrieving all webhooks, it does not explicitly mention when to use this tool versus get_webhook, create_webhook, update_webhook, or delete_webhook. No direct alternative guidance is provided.

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

Deploy Server

Other Tools