Skip to main content
Glama
Sign In
SeaTable MCP

SeaTable MCP

Official
by seatable
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_row_activities

Read-onlyIdempotent

Retrieve the change history of a specific row, showing who made changes, when, and the old and new values. Returns 25 activities per page, with pagination support.

Instructions

Get the change history of a specific row. Returns a list of activities showing who changed what and when, including old and new values. 25 activities per page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "table": "<table>",
      "row_id": "<row_id>"
    },
    "name": "get_row_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableYesTable name (used for context in the response)
row_idYesRow ID to get the activity history for
pageNoPage number (default 1, 25 activities per page)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.2

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so behavior is safe. The description adds pagination detail (25 per page) which is useful, but doesn't mention limits on history retention or performance implications.

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?

Two sentences clearly convey purpose and a key behavioral detail. No waste.

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 read-only history tool with full schema descriptions and annotations, the description is adequate. Missing details on ordering (chronological?) or whether all changes are recorded, but sufficient for selection.

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% and each parameter has a description. The tool description adds '25 activities per page' beyond schema, but does not explain the 'table' parameter's role beyond context.

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?

Clearly states that the tool retrieves change history for a specific row, including who changed what and when, with old and new values. This distinguishes it from siblings like get_row (current state) or list_rows (list of rows).

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?

States when to use: to get change history of a specific row. Does not explicitly exclude other tools, but the narrow purpose implies limited usage. Could mention alternatives like get_row or list_rows for non-historical data.

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