feedbackFree. 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.
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | other | |
| route | No | the route the feedback is about, if any | |
| contact | No | optional: how we can reach you or your operator | |
| message | Yes | what worked, what did not, what you miss; no secrets or private data |
Changes observed during successful MCP inspections.
Input schema / properties / route / enumPrevious 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"
+]Input schema / properties / route / enumPrevious 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"
+]Input schema / properties / route / enumPrevious 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"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare non-destructive write, non-idempotent, closed-world behavior. The description adds valuable context beyond annotations: rate limiting (a few messages an hour), human review, no payment/account, and a privacy hint in the schema. It does not contradict annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Short, front-loaded, and every sentence adds value. 'Free' immediately sets cost context, followed by purpose, review process, and constraints—no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given a simple form with four parameters (one required) and no output schema, the description covers what the tool does, cost, rate limit, human review, and privacy guidance. Minor gaps: it does not describe a confirmation or return behavior, but that is less critical here.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 75% with explicit descriptions for route, contact, and message. The description's phrasing 'a bug, an idea or a thanks' loosely maps to the kind enum, but it does not add meaning beyond what the schema provides for the other parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: send feedback to the people who run the service. The examples (bug, idea, thanks) clarify scope, and it is trivially distinguished from all sibling tools, which are data-retrieval tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Clear context for when to use it: to report what worked, failed, or is missing. It adds constraints (limited to a few messages an hour, no account) but does not explicitly state when not to use it or name alternatives, though no feedback alternative exists.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.