Skip to main content
Glama

smartsheet_list_row_discussions

List all discussions attached to a specific row in Smartsheet by specifying sheet and row IDs. Supports pagination and include flags.

Instructions

List discussions on a specific row.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number.
row_idYesRow ID inside the sheet.
includeNoOptional include flags.
sheet_idYesSmartsheet sheet ID.
page_sizeNoResults per page.
include_allNoIf true, return all results (ignores page/page_size).
Behavior2/5

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

With no annotations, the description carries the full burden. It states a read operation but omits behavioral traits such as pagination, ordering, or the structure of the returned data. The schema covers parameters, but behavior beyond 'list' is undisclosed.

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 a single, concise sentence with no wasted words. It is front-loaded and easy to parse, though it offers limited additional information.

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?

Missing an output schema and annotations, the description should compensate but does not. It fails to explain return format, pagination behavior, or how discussions relate to rows, leaving the agent with insufficient context.

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?

Schema coverage is 100%, so the parameters are well-documented in the schema. The description adds no additional meaning beyond what the schema provides, meeting the baseline but not exceeding it.

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?

The description 'List discussions on a specific row' clearly states the action (list) and the resource (discussions on a row), which distinguishes it from sibling tools like smartsheet_list_sheet_discussions (discussions on a sheet). However, it does not explicitly mention the required identifiers (sheet_id, row_id) or differentiate from 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 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 (e.g., smartsheet_list_sheet_discussions, smartsheet_get_discussion). It does not indicate prerequisites, exclusions, or typical use cases.

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/Kcrong/smartsheet-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server