Skip to main content
Glama

List Card Comments

fizzy_get_card_comments
Read-only

Fetch all comments on a card in chronological order, showing authors, timestamps, and reaction counts. Optionally include attachment metadata for each comment.

Instructions

Get all comments on a card in chronological order. Returns comment text (HTML), authors, timestamps, and reaction counts. Use this to review discussion and feedback on a card. The result is the complete thread: every upstream page is fetched server-side, so there is no page parameter and nothing further to request. Use fields='summary' to drop the duplicated HTML body and the repeated per-comment card/creator detail — comment text itself is never truncated in either mode. Attachments posted in a comment appear only as raw markup inside the HTML body, which fields='summary' drops entirely. Pass include_attachments=true to add a per-comment 'attachments' array with each file's filename, content_type, byte_size, dimensions and signed_id — it works in both modes — then pass that signed_id and filename to fizzy_get_attachment to actually see an image.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoResponse projection. 'full' (the default — used when this parameter is omitted) returns every field exactly as the API provides it, unchanged from prior behavior. 'summary' strips large, rarely-needed fields — full HTML/rich-text bodies and descriptions, duplicated plain-text/HTML pairs, and repeated embedded objects like the full creator or card — keeping only IDs, names, and short previews. Summary responses are typically 4x to over 100x smaller depending on the tool. Prefer 'summary' when scanning, searching, or listing many results; switch to 'full' (or a single-item fetch tool) once you need complete detail on a specific item.
card_idNoThe unique card identifier (numeric string, e.g., '67890'). Provide either card_id or card_number. Get available card IDs from fizzy_get_cards.
card_numberNoThe card number - the visible ID shown on the board (e.g., '#123'). Provide either card_id or card_number.
account_slugYesThe account slug identifier (e.g., '123456' or '/123456'). This identifies which Fizzy account to operate on. Get available account slugs from fizzy_get_identity or fizzy_get_accounts.
include_attachmentsNoSet true to add an 'attachments' array parsed out of the rich-text HTML: each file's filename, content_type, byte_size, width, height, signed_id, url and preview_url. Attachments are otherwise visible only as raw <action-text-attachment> markup inside the HTML, and not at all in the plain-text rendering. Pass the returned signed_id and filename to fizzy_get_attachment to actually see an image. Omitting this parameter (the default) leaves the response exactly as it was before this option existed.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses important behaviors: server-side fetching of every upstream page, no pagination parameter, comment text never being truncated, raw <action-text-attachment> markup behavior, and the effects of include_attachments. This gives the agent a clear model of what the operation does and what to expect in the response.

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?

The description is front-loaded with the core purpose, then flows naturally into response behavior, fields projection, and attachment handling. Each sentence contributes new, actionable information without redundant filler, and the length is justified by the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 covers the key return contents (text, authors, timestamps, reaction counts), the complete-thread guarantee, the fields projection options, and the attachment retrieval workflow. It is sufficient for an agent to select and invoke the tool correctly with no lingering behavioral gaps.

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

Parameters5/5

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

Although schema coverage is 100%, the description adds meaningful parameter semantics: fields='summary' drops duplicated HTML and repeated card/creator detail, comment text remains untruncated, and include_attachments=true produces an attachments array with signed_id for use with fizzy_get_attachment. This goes well beyond the schema's baseline 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?

The description opens with a specific verb and resource: 'Get all comments on a card in chronological order.' It further clarifies the result scope by stating 'the complete thread... no page parameter and nothing further to request,' which differentiates it from single-comment tools like fizzy_get_comment.

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?

The description gives clear usage context: 'Use this to review discussion and feedback on a card,' and explains the complete-thread behavior so an agent knows no pagination is needed. It provides guidance on when to use fields='summary' versus 'full' and how to retrieve attachments, though it does not explicitly state alternatives like fizzy_get_comment for fetching a single comment.

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

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/Fabric-Pro/fizzy-mcp'

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