Skip to main content
Glama
Sign In

PageHub

by dev.pagehub
OverviewDiscussionsAdmin

Import collection CSV

import_collection_csv
Destructive

Import rows from CSV text or an uploaded CSV/TSV/XLSX file (exactly one of csv | mediaId); header columns match field keys (unmatched ignored). mode: append (default), replace (deletes existing rows first), upsert (by an externalId or id column). ~8MB cap. Plan-gated.

Input Schema

NameRequiredDescriptionDefault
idNoSite id.
csvNoCSV text with a header row.
modeNoMerge mode. Default append.
slugYesCollection slug.
mediaIdNoAn uploaded CSV/TSV/XLSX file's mediaId (the agent gets this for attached files). Use this instead of csv when the data was uploaded — never retype rows.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / mediaId
      Added value: +{
+  "description": "An uploaded CSV/TSV/XLSX file's mediaId (the agent gets this for attached files). Use this instead of csv when the data was uploaded — never retype rows.",
+  "maxLength": 100,
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "slug",
-  "csv"
-]New value: +[
+  "slug"
+]
  2. Changed3 schema fields changed
    • addedInput schema / properties / id
      Added value: +{
+  "description": "Site id.",
+  "maxLength": 256,
+  "type": "string"
+}
    • removedInput schema / properties / site_id
      Removed value: -{
-  "maxLength": 256,
-  "type": "string"
-}
    • addedInput schema / properties / slug / description
      Added value: +"Collection slug."
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: replace deletes existing rows first, upsert matches on an externalId/id column, header/field matching rules, an ~8MB size cap, and that the operation is plan-gated. These disclosures (destructive replace semantics, cap, entitlement) go well past destructiveHint=true.

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?

A single dense paragraph, front-loaded with the input-source rule and mode behavior. Every clause carries information, though the semicolon-packed style is slightly heavy.

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 5-param mutation tool with no output schema and full annotation coverage, the description covers inputs, modes, limits, and entitlement. It omits what the call returns (e.g. imported-row counts) and pagination/status behavior, which is a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description earns above that by explaining mode behaviors (append default, replace deletes first, upsert keyed by externalId/id), header-key matching with unmatched ignored, and the 8MB cap — genuine meaning beyond the field descriptions.

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 (Import) and resource (rows into a collection from CSV/TSV/XLSX), and is clearly distinguishable from siblings like create_collection_rows or import_site. An agent immediately knows this bulk-imports tabular data.

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 selection rule between the two input sources ('exactly one of csv | mediaId') and explains mode semantics. It doesn't explicitly route to alternative sibling tools (e.g. single-row creation), but the when-to-use context is strong.

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

All PageHub toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources