Skip to main content
Glama
Sign In
smartsheet-mcp

smartsheet-mcp

by Kcrong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

smartsheet_list_webhooks

Retrieve all webhooks registered by your authenticated Smartsheet token, with optional pagination and filtering to include all results.

Instructions

List webhooks registered by the authenticated token.

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": "smartsheet_list_webhooks"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number.
page_sizeNoResults per page.
include_allNoIf true, return all results (ignores page/page_size).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description must bear the load. It only mentions authentication scope ('registered by the authenticated token') but fails to disclose pagination behavior, rate limits, or the effect of the include_all parameter. The minimal description does not adequately inform the agent of operational traits.

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 sentence of six words, highly concise with no redundant information. Every word earns its place.

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?

Given no output schema and three parameters, the description is too minimal. It does not explain the return format, the meaning of pagination, or the behavior of include_all. While the schema covers parameters, the description lacks completeness for a list tool.

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% description coverage for all three parameters (page, page_size, include_all), so the description adds no extra meaning. The description itself does not mention any parameters or provide additional context beyond 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 verb 'List', the resource 'webhooks', and the scope 'registered by the authenticated token'. It distinguishes itself from siblings like smartsheet_get_webhook (singular) and other list tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

While no explicit when/not-to-use guidance is given, the name and description inherently indicate this is for listing all webhooks. The sibling name smartsheet_get_webhook implies a singular retrieval, but the description does not explicitly contrast them.

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