Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

render-data-table

Renders any list result as an interactive table with client-side sort, search and pagination, so you can explore keywords, pages, movers or backlinks directly in chat.

Instructions

Render an interactive table with client-side sort, search and pagination from any list result — top keywords, top pages, biggest movers, prompts, backlinks and more. Columns are typed from the data and array cells stay as chips. Auto-called when a list tool returns render_with: render-data-table. Free.

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": "render-data-table"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and it does disclose meaningful behavior: sorting/search/pagination happen client-side, columns are typed from the data, array cells become chips, and it is auto-invoked by list tools. It also notes the "Free" cost profile, which is useful for invocation decisions. It does not say what happens if invoked manually without list data or how it behaves on empty/malformed input.

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 tightly written sentences that front-load the core action and capabilities, then follow with the invocation rule and cost note. Every clause adds information; nothing is redundant with the tool name.

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?

With no output schema, the description correctly frames the result as a rendered interactive table rather than a data payload, and the auto-call rule tells an agent how it will normally be reached. The remaining gap is manual-invocation input expectations, which is minor for a normally auto-triggered renderer.

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?

Zero declared parameters, so the baseline is 4, but the schema is an open object (additionalProperties: true) with no documented payload shape, and the description does not explain what data an agent would pass if calling it directly. That ambiguity is a real gap for a tool whose input is implicitly "a list result."

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?

States a specific verb and resource ("Render an interactive table") plus the capabilities (client-side sort, search, pagination) and the input source (any list result). The enumerated examples (top keywords, top pages, biggest movers, prompts, backlinks) make it clearly distinguishable from sibling renderers like render-scorecard and render-time-series-chart.

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?

Gives a clear trigger: "Auto-called when a list tool returns render_with: render-data-table" and "from any list result." It does not state when an agent should NOT use this versus the chart/scorecard renderers, but the auto-call rule and the list-result precondition are strong, actionable context.

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