Skip to main content
Glama

Send feedback

feedback

Free. Tell the people who run this service what worked, what failed or what you miss: a bug, an idea or a thanks. A person reads it. No payment, no account; limited to a few messages an hour.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "message": "<message>"
    },
    "name": "feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoother
routeNothe route the feedback is about, if any
contactNooptional: how we can reach you or your operator
messageYeswhat worked, what did not, what you miss; no secrets or private data

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / route / enum
      Previous value: -[
      -  "unblock",
      -  "instagram",
      -  "google-maps",
      -  "tiktok",
      -  "linkedin",
      -  "youtube",
      -  "twitter",
      -  "reddit",
      -  "amazon",
      -  "google-search",
      -  "google-maps-reviews",
      -  "youtube-transcript",
      -  "screenshot",
      -  "linkedin-jobs",
      -  "indeed-jobs",
      -  "shopify-products",
      -  "google-news",
      -  "amazon-reviews",
      -  "google-play-reviews",
      -  "linkedin-company",
      -  "web-search",
      -  "x-replies",
      -  "youtube-comments",
      -  "tiktok-comments",
      -  "instagram-comments",
      -  "ebay-sold",
      -  "meta-ads",
      -  "linkedin-profile-email",
      -  "linkedin-posts",
      -  "facebook-page",
      -  "facebook-posts",
      -  "facebook-comments",
      -  "domain-contacts",
      -  "maps-contacts",
      -  "email-verify",
      -  "search-plus"
      -]New value: +[
      +  "unblock",
      +  "instagram",
      +  "google-maps",
      +  "tiktok",
      +  "linkedin",
      +  "youtube",
      +  "twitter",
      +  "reddit",
      +  "amazon",
      +  "google-search",
      +  "google-maps-reviews",
      +  "youtube-transcript",
      +  "screenshot",
      +  "linkedin-jobs",
      +  "indeed-jobs",
      +  "shopify-products",
      +  "google-news",
      +  "amazon-reviews",
      +  "google-play-reviews",
      +  "linkedin-company",
      +  "web-search",
      +  "x-replies",
      +  "youtube-comments",
      +  "tiktok-comments",
      +  "instagram-comments",
      +  "ebay-sold",
      +  "meta-ads",
      +  "linkedin-profile-email",
      +  "linkedin-posts",
      +  "facebook-page",
      +  "facebook-posts",
      +  "facebook-comments",
      +  "domain-contacts",
      +  "maps-contacts",
      +  "email-verify",
      +  "instagram-profile",
      +  "instagram-reels",
      +  "linkedin-post-search",
      +  "facebook-group-posts",
      +  "linkedin-company-search",
      +  "linkedin-comments",
      +  "search-plus"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / route / enum
      Previous value: -[
      -  "unblock",
      -  "instagram",
      -  "google-maps",
      -  "tiktok",
      -  "linkedin",
      -  "youtube",
      -  "twitter",
      -  "reddit",
      -  "amazon",
      -  "google-search",
      -  "google-maps-reviews",
      -  "youtube-transcript",
      -  "screenshot",
      -  "linkedin-jobs",
      -  "indeed-jobs",
      -  "shopify-products",
      -  "google-news",
      -  "amazon-reviews",
      -  "google-play-reviews",
      -  "linkedin-company",
      -  "web-search",
      -  "x-replies",
      -  "youtube-comments",
      -  "tiktok-comments",
      -  "instagram-comments",
      -  "ebay-sold",
      -  "meta-ads",
      -  "linkedin-profile-email",
      -  "linkedin-posts",
      -  "search-plus"
      -]New value: +[
      +  "unblock",
      +  "instagram",
      +  "google-maps",
      +  "tiktok",
      +  "linkedin",
      +  "youtube",
      +  "twitter",
      +  "reddit",
      +  "amazon",
      +  "google-search",
      +  "google-maps-reviews",
      +  "youtube-transcript",
      +  "screenshot",
      +  "linkedin-jobs",
      +  "indeed-jobs",
      +  "shopify-products",
      +  "google-news",
      +  "amazon-reviews",
      +  "google-play-reviews",
      +  "linkedin-company",
      +  "web-search",
      +  "x-replies",
      +  "youtube-comments",
      +  "tiktok-comments",
      +  "instagram-comments",
      +  "ebay-sold",
      +  "meta-ads",
      +  "linkedin-profile-email",
      +  "linkedin-posts",
      +  "facebook-page",
      +  "facebook-posts",
      +  "facebook-comments",
      +  "domain-contacts",
      +  "maps-contacts",
      +  "email-verify",
      +  "search-plus"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / route / enum
      Previous value: -[
      -  "unblock",
      -  "instagram",
      -  "google-maps",
      -  "tiktok",
      -  "linkedin",
      -  "youtube",
      -  "twitter",
      -  "reddit",
      -  "amazon",
      -  "google-search",
      -  "google-maps-reviews",
      -  "youtube-transcript",
      -  "screenshot",
      -  "linkedin-jobs",
      -  "indeed-jobs",
      -  "shopify-products",
      -  "google-news",
      -  "amazon-reviews",
      -  "google-play-reviews",
      -  "linkedin-company",
      -  "web-search",
      -  "x-replies",
      -  "youtube-comments",
      -  "tiktok-comments",
      -  "instagram-comments",
      -  "ebay-sold",
      -  "meta-ads",
      -  "search-plus"
      -]New value: +[
      +  "unblock",
      +  "instagram",
      +  "google-maps",
      +  "tiktok",
      +  "linkedin",
      +  "youtube",
      +  "twitter",
      +  "reddit",
      +  "amazon",
      +  "google-search",
      +  "google-maps-reviews",
      +  "youtube-transcript",
      +  "screenshot",
      +  "linkedin-jobs",
      +  "indeed-jobs",
      +  "shopify-products",
      +  "google-news",
      +  "amazon-reviews",
      +  "google-play-reviews",
      +  "linkedin-company",
      +  "web-search",
      +  "x-replies",
      +  "youtube-comments",
      +  "tiktok-comments",
      +  "instagram-comments",
      +  "ebay-sold",
      +  "meta-ads",
      +  "linkedin-profile-email",
      +  "linkedin-posts",
      +  "search-plus"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / route / enum
      Previous value: -[
      -  "unblock",
      -  "instagram",
      -  "google-maps",
      -  "tiktok",
      -  "linkedin",
      -  "youtube",
      -  "twitter",
      -  "reddit",
      -  "amazon",
      -  "google-search",
      -  "google-maps-reviews",
      -  "youtube-transcript",
      -  "screenshot",
      -  "linkedin-jobs",
      -  "indeed-jobs",
      -  "google-news",
      -  "amazon-reviews",
      -  "web-search",
      -  "x-replies",
      -  "youtube-comments",
      -  "tiktok-comments",
      -  "instagram-comments",
      -  "search-plus"
      -]New value: +[
      +  "unblock",
      +  "instagram",
      +  "google-maps",
      +  "tiktok",
      +  "linkedin",
      +  "youtube",
      +  "twitter",
      +  "reddit",
      +  "amazon",
      +  "google-search",
      +  "google-maps-reviews",
      +  "youtube-transcript",
      +  "screenshot",
      +  "linkedin-jobs",
      +  "indeed-jobs",
      +  "shopify-products",
      +  "google-news",
      +  "amazon-reviews",
      +  "google-play-reviews",
      +  "linkedin-company",
      +  "web-search",
      +  "x-replies",
      +  "youtube-comments",
      +  "tiktok-comments",
      +  "instagram-comments",
      +  "ebay-sold",
      +  "meta-ads",
      +  "search-plus"
      +]
  5. Added

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (write, non-destructive, non-idempotent), the description discloses that submission is free, requires no account or payment, is read by a human, and is rate limited to a few messages per hour — genuinely useful behavioral context an agent cannot infer from annotations. It stops short of saying what confirmation or error the caller receives.

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 short sentences, front-loaded with the key qualifier "Free." and zero filler; each sentence contributes a distinct fact (purpose, channel, cost/auth, rate limit).

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 simple four-parameter submission tool with no output schema, the description covers what to send, who reads it, the cost/account model, and the throttle. Only the post-submit outcome (acknowledgement, error behavior) is unstated, which is a minor gap.

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 75% and already documents `route`, `contact`, and `message`; the description only loosely echoes the `kind` categories (bug, idea, thanks). It adds no detail on how to choose a `route` or what a good `contact` value looks like, so the schema does the heavy lifting.

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 states a specific action ("Tell the people who run this service what worked, what failed or what you miss") with concrete feedback categories, so the agent knows this is a message-submission tool, not a data-retrieval route. It never explicitly contrasts itself with the sibling scraper tools even though the `route` parameter enumerates their names, which could momentarily suggest this fetches per-route 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?

Clear usage triggers are given: a bug, an idea, or a thanks, plus the extras "what failed" and "what you miss." There are no explicit exclusions or named alternatives, but since no sibling tool covers this function the practical guidance is sufficient.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources