Skip to main content
Glama

YouSpot

by com.youspot
OverviewDiscussionsAdmin

Create tracker

create_tracker

Set up a standing search the user wants watched — 'track LinkedIn posts that mention hubspot', 'track tweets mentioning @dharmesh', 'watch acme.com/pricing for changes'. query is what to watch for; tracker_type says where to watch (LinkedIn posts unless they ask for tweets/X or a specific page URL — a URL to watch means web_page, with the URL in url and query as a short label for it). linkedin_post and twitter_search requests become a daily cloud agent that emails a digest of new posts; web_page creates a tracker in their brain that runs daily and emails changes, filtered by the prompt. Always give the user the returned page_url as a link — that page is where they review and manage it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoweb_page trackers only: the page URL to watch for changes.
queryYesThe search keywords to watch for (e.g. 'hubspot').
promptYesThe user's tracking request in their own words, verbatim, filters included (e.g. 'Track linkedin posts that mention hubspot and have more than 10 likes'). Stored on the tracker and later applied as a filter to what the search returns.
tracker_typeNoWhere to watch. Defaults to linkedin_post.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / tracker_type / enum
      Previous value: -[
-  "linkedin_post",
-  "twitter_search",
-  "google_search",
-  "web_page"
-]New value: +[
+  "linkedin_post",
+  "twitter_search",
+  "web_page"
+]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Discloses significant side effects: daily execution, email digests for certain tracker types, and a web_page tracker running in 'their brain'. Also instructs the agent to always provide the returned page_url as a link. This goes well beyond the minimal readOnlyHint annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is somewhat long and uses parenthetical examples, but it's well-organized and each sentence adds necessary clarification. Slightly verbose but not to the point of confusion.

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?

Given the four parameters, an enum, and distinct behaviors for each tracker type, the description fully equips an agent to invoke the tool correctly. It explains defaults, examples, output handling (page_url link), and the overall purpose. No missing critical context.

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?

The schema already covers all 4 parameters with descriptions, and the tool description adds meaningful context: clarifies the difference between query (what to watch for) and prompt (verbatim user request with filters), explains the default tracker_type, and specifies the role of url for web_page type. This is rich additive detail.

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?

Clearly states the tool creates a tracking mechanism for standing searches, with specific examples of user requests. It distinguishes itself from sibling tools like search_linkedin_posts and search_tweets by emphasizing the persistent, ongoing nature of the tracker.

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?

Provides strong guidance on when to use the tool (when the user wants a standing search) and explains how different tracker types behave. It doesn't explicitly contrast with one-off search tools, but the examples and behavior descriptions make the intended usage clear.

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

All YouSpot toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources