Skip to main content
Glama
joffreyBerrier

feedbug-mcp

by joffreyBerrier
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Read the browser environment of a bug

feedbug_get_diagnostics
Read-onlyIdempotent

Retrieves browser diagnostic data for a reported bug: page URL, viewport size, user agent, and reporter name. Use it to reproduce device-specific issues or determine if a problem is limited to a particular environment.

Instructions

Read the browser environment a bug was reported from.

Returns: a JSON object with the page URL, the viewport size, the user agent and the name of the reporter. Use when: you need to reproduce a bug under the same browser, screen size or account, or to judge whether a report is device-specific. Do not use when: you also want the screenshot, the DOM or the tracker link — this is a strict subset of feedbug_get_bug, so one call there replaces this one. Behavior: read-only and idempotent, scoped by FEEDBUG_PROJECT_KEY to a single project. Fields the widget could not capture come back null; an unknown id returns a "Bug not found" error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesBug UUID as returned by feedbug_list_bugs, or the tracker identifier such as PRE-13, matched case-insensitively. Ids belonging to another project are rejected.

Schema Changelog

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

  1. Changed1 schema field changedv1.1.2
    • changedInput schema / properties / id / description
      Previous value: -"Feedback UUID or Linear identifier (e.g. PRE-13)"New value: +"Bug UUID as returned by feedbug_list_bugs, or the tracker identifier such as PRE-13, matched case-insensitively. Ids belonging to another project are rejected."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Adds context beyond annotations: read-only & idempotent (echoed and expanded), scoped by FEEDBUG_PROJECT_KEY, null fields for missing data, and error handling for unknown IDs. No contradiction with annotations.

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?

Four tight sentences, front-loaded with main action. Uses clear section headers (Returns, Use when, Do not use when, Behavior). No wasted words.

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?

Covers input, output (explicit JSON fields), error cases, scope (single project), and relationship to sibling tools. No output schema, but description fully compensates.

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 describes the 'id' parameter in detail. Description adds no additional parameter information beyond schema, so baseline 3 is appropriate.

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?

Clear verb 'read' and resource 'browser environment'. Specifies returned fields (page URL, viewport size, user agent, reporter). Distinguishes from sibling feedbug_get_bug which includes more data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly provides 'Use when' and 'Do not use when' sections. Tells when to reproduce bugs and when to prefer feedbug_get_bug instead.

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

Install Server

Other Tools

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/joffreyBerrier/feedbug-mcp'

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