Skip to main content
Glama

Serpapi

by io.github.pipeworx-io

Subscribe to Alerts

subscribe
Idempotent

Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id. Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions). Supported types: "sec_8k" (8-K filings matching ticker + item codes — e.g. items:["5.02"] = officer change), "polymarket_edge" (Polymarket↔Kalshi cross-venue mispricings — params:{topic:"fed"}), "fred_series" (new FRED observations — params:{series_id:"UNRATE"}). Delivery channels: feed (always on — pull via recent_alerts or GET registry.pipeworx.io/alerts.json), and optionally email (set delivery:{email:"you@x.com"}) or sms (delivery:{sms:"+15551234567"} — phone must be verified at /account first; 10/day cap).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesSubscription type.
paramsYesType-specific filter. sec_8k: {ticker:"AAPL", items?:["5.02","1.01"]}. polymarket_edge: {topic:"fed", min_spread_bps?:500}. fred_series: {series_id:"UNRATE"}. patent_grant: {applicant:"Apple Inc."}. clinical_trial: {sponsor?:"Pfizer", condition?:"lung cancer", phase?:"PHASE3"} (sponsor or condition required).
deliveryNoOptional delivery channels in addition to the always-on persistent feed. {email:"you@x.com"} sends a templated alert per fired event. {sms:"+15551234567"} sends an SMS per event — must match the verified phone on the caller's account (verify at https://pipeworx.io/account first; 10/day cap). {webhook:"https://..."} POSTs each event JSON to your endpoint, HMAC-signed — the response includes delivery.webhook_secret (whsec_…) ONCE; verify X-Pipeworx-Signature = sha256 HMAC of "<X-Pipeworx-Timestamp>.<raw body>". Auto-disabled after 10 consecutive failing runs.

TDQS

A4.7/5.0
Behavior5/5

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

The description adds significant behavioral context beyond annotations: it explains that subscriptions require OAuth, details each type's parameters, delivery channels (feed always on, email/SMS/webhook with specific constraints like SMS cap and webhook auto-disable), and that a subscription id is returned. No contradiction with annotations (readOnlyHint=false, idempotentHint=true, etc.).

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 relatively long but efficiently packs all necessary information. It front-loads the main purpose and then systematically covers types and delivery. A more structured layout could improve readability, but it is not wasteful.

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 lack of output schema, the description fully covers the return value (subscription id). It explains all supported types, parameters, delivery options with constraints, and prerequisites. No critical gaps remain for an agent to invoke the tool correctly.

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 description adds substantial meaning beyond the schema: it provides concrete examples for each type (e.g., sec_8k items, polymarket_edge topic, fred_series series_id), explains param structure, and for delivery gives detailed info on webhook signing, SMS verification, and email validation. Schema coverage is 100% and description enriches it greatly.

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?

The description clearly states the tool's action ('Create a proactive monitoring subscription to a live-data event stream') and its return value ('Returns the new subscription id'). It lists supported types and delivery channels, and distinguishes from sibling tools like list_subscriptions and unsubscribe by focusing on creation.

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?

The description provides explicit guidance on prerequisites (Pipeworx OAuth account, anonymous/BYO cannot persist), supported subscription types with examples, and delivery channel options. It does not explicitly specify when not to use this tool versus alternatives, but the context is clear enough for most cases.

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

All Serpapi toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation3/5

Many tools have overlapping purposes, such as ask_pipeworx, ask_pipeworx_grounded, deep_research, and bet_research all querying data but with nuanced differences. The descriptions help but boundaries remain fuzzy, especially between ask_pipeworx and deep_research for broad vs. single lookups. Overall moderate ambiguity.

Naming Consistency2/5

Naming is inconsistent: some tools use snake_case (ask_pipeworx, ai_visibility_check), others use camelCase (serpapi_google_jobs), and patterns vary widely (e.g., pipeworx_feedback vs. compare_entities). Only the serpapi_google_* group follows a consistent pattern.

Tool Count3/5

36 tools is on the high side for a single server, with many meta-tools (discover_tools, suggest_questions) and niche prediction market tools. The scope seems overly broad, covering data lookup, prediction markets, memory, and subscriptions, which could be streamlined to a more focused set.

Completeness3/5

The server covers a wide range of domains (financial, economic, news, drugs, prediction markets, Google services), but lacks direct web search and write/update capabilities. While the coverage is broad, there are notable gaps (e.g., no generic web search, limited tool for modifying data) for a data-focused server.

Resources