Skip to main content
Glama
valentil

FeatureBoard MCP Server

by valentil
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

Configure site analytics

set_site_analytics
Idempotent

Add site-wide analytics tracking by injecting a Plausible, Google Analytics, or custom script into every page's head, or disable to remove it.

Instructions

Add an analytics snippet to every page of the site's : Plausible or Google Analytics by id, or a raw custom . Re-renders the site. Set enabled:false to remove it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoPlausible domain or GA measurement id (e.g. G-XXXX).
enabledNo
projectYes
snippetNoRaw <script> for provider 'custom'.
providerNo

Tool Definition Quality

A3.5/5.0
Behavior4/5

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

Annotations already indicate idempotent and non-destructive behavior. The description adds valuable context: re-renders the site and how to remove analytics via enabled:false. This well complements the annotations without contradiction.

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 a single, well-structured sentence that efficiently conveys the tool's purpose, parameters, and behavior. No redundant information.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 5 parameters, no output schema, and siblings, the description omits the required 'project' parameter and lacks usage guidance. It covers key behavioral aspects but is not fully complete for an agent to use confidently.

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 low (40%). The description explains most parameters (id, provider, snippet, enabled) but fails to mention the required 'project' parameter. It adds meaning beyond schema but not for all parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool adds an analytics snippet to every page's <head>, with options for Plausible, GA, or custom. However, it does not differentiate from sibling tools like 'set_analytics_config' or 'auto_configure_analytics', which may have overlapping functionality.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, limitations, or mention that 'auto_configure_analytics' might be a better choice for automatic configuration.

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/valentil/featureboard-mcp'

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