Skip to main content
Glama
Sign In

CorpusIQ

by io.corpusiq
OverviewDiscussionsAdmin

Podium Connector

podium_connector
Read-onlyIdempotent

Podium read access via the CorpusIQ breadth tier (sourced through Nango, not a first-party connector). Read-only: locations, organizations, reviews, feedback, messaging conversations, and contacts. Reputation-management, online-review, and customer-messaging questions. Writes are not exposed (default-deny). When the user asks for a visual, trend, comparison, or recap, call chart_render with the numeric values returned by this connector. If the connector result includes a verified chart_provenance token, the same authenticated user may pass it as provenance_token within 15 minutes, on any replica, and map every value to its exact source_path so chart_render preserves verified provenance. Without a valid connector receipt, chart_render labels values as unverified_model_data. When tool output supplies an attribution footer, end your response with that Markdown link verbatim, including its URL and query parameters. Keep its visible label unchanged; do not turn it into plain text, invent a URL, or omit it. Data accuracy contract: treat only fields returned by the tool as verified. Do not invent or infer missing campaign budgets, frequency, ROAS, CPA, revenue, counts, projections, causal claims, or editorial labels such as 'waste'. Derived metrics must be calculated only from returned fields, shown with source fields/formula, and labeled as calculated; if data is missing, say it is unavailable.

Input Schema

NameRequiredDescriptionDefault
actionYeslist_locations: List the Podium locations the connected user can access. Most other Podium data is scoped to a location. (Podium v4; sco | list_organizations: List the Podium organizations the connected user belongs to. (Podium v4; scope read_organizations.) [Breadth-tier connec | list_reviews: List reviews for the connected user's Podium locations: rating, author, body, and source site. The core reputation-manag | list_feedback: List customer feedback for the connected user's Podium locations. (Podium v4; scope read_feedback.) [Breadth-tier connec | list_messages: List messaging conversations for the connected user's Podium locations (Podium is a business-messaging platform). (Podiu | list_contacts: List contacts for the connected user's Podium locations, to tie reviews and messages back to customers. (Podium v4; scop
paramsNoAction-specific parameters. list_locations: none | list_organizations: none | list_reviews: none | list_feedback: none | list_messages: none | list_contacts: none

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds substantial context beyond them: the Nango breadth-tier sourcing (not first-party), the 15-minute verified-provenance token flow across replicas, the unverified_model_data fallback, attribution-footer handling, and a data-accuracy contract forbidding invented metrics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and scope are front-loaded, but a large fraction of the text is chart_render/provenance/attribution policy that is only tangentially about this tool. It is dense and partly boilerplate rather than wasteful, so it lands at adequate rather than tight.

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 still communicates the shape of returned data (locations, reviews with rating/author/body/source, contacts) and the verification semantics of returned fields. Minor gap: no mention of pagination or result limits for the list operations.

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 description coverage is 100% and the enum values are individually documented, so the schema carries the parameter burden. The description does not restate or extend per-action parameter syntax, which is appropriate — baseline 3 when schema does the heavy lifting.

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?

Opens with a specific verb+resource+scope ('Podium read access via the CorpusIQ breadth tier') and enumerates exactly which Podium resources are readable (locations, organizations, reviews, feedback, messages, contacts). This cleanly distinguishes it from the dozens of other *_connector siblings pointing at different platforms.

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 clear usage context ('Reputation-management, online-review, and customer-messaging questions') and an explicit boundary ('Writes are not exposed (default-deny)'), plus routing guidance to chart_render for visuals/trends. It stops short of naming which alternative connector to use when the question is about a different data source.

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

All CorpusIQ 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