Skip to main content
Glama

PitchSpark: Pre-Seed & Seed Deal Flow

Save a startup search (query and filters) to re-run later

pitchspark_save_search_v1
Idempotent

Save a search (the query and filters of pitchspark_search_pitches_v2) under the caller's API key, to list and re-run later with pitchspark_list_saved_searches_v1. Use when: the investor asks to save or remember a search. Do not use for: alerts (not delivered yet: saving does not send anything), running the search (pitchspark_search_pitches_v2). Requires a PitchSpark API key with the searches:write scope (keys without a scope list hold it). Idempotent: the same normalised query and filters under the same key returns the existing saved search (status "already_saved") and writes nothing new. At most 20 saved searches per key (status "limit_reached"); 50 saves per key per UTC day (RATE_LIMITED). Do not put personal data (names, emails, phone numbers, anything about a person) in "name" or "query": they are stored for up to 180 days. Emails and phone numbers that do appear are stored as [redacted]. Saved searches are deleted 180 days after they were last saved, and with the account. Returns {"status","saved_search","max_per_key","next_steps"}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pitchspark_save_search_v1"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoA short label, e.g. "Seed fintech in Europe".
sortNorelevance (keyword + synonym score; "top scoring" in the query still orders by score), score (public score, pitches without one last), recency (newest listing first), most_viewed_by_investors (Pitch.views_count, all viewers), recently_updated.relevance
queryNoOptional plain-English request, 1 to 200 characters, read by the same rules as pitchspark_search_pitches_v1 (sector, stage, place, raise, score and traction cues; quotes and "not X"). Keyword + synonym matching, not semantic search.
stageNoFunding stage or list. "early" means pre_seed, seed and series_a.
sectorNoSector key or list of up to 10 (primary or additional sector). Keys: fintech, healthtech, saas, marketplace, ai_ml, consumer, enterprise, climate, edtech, crypto, biotech, hardware, gaming, real_estate, food_beverage, fashion, travel, sports, media, femtech, cybersecurity, dev_tools, ecommerce, logistics, mobility, hr_tech, legal_tech, insurtech, proptech, agtech, energy, robotics, govtech, hospitality, other.
locationNoHQ region key or list: us, canada, latam, uk, europe, mea, apac, global_remote.
min_scoreNoPublic PitchSpark score at least this (values under 70 are read as 70; pitches without a public score are left out).
green_flagsNoTraction signal: at least one of these founder-chosen green flags (e.g. "Profitable", "Signed LOI").
has_tractionNoTraction signal: true = only pitches with a public traction note.
max_raise_usdNoRaise at most this many US dollars (disclosed asks only).
min_raise_usdNoRaise at least this many US dollars (disclosed asks only).
created_within_daysNoRecency: listed on PitchSpark within this many days.
updated_within_daysNoRecency: pitch updated within this many days.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent only when the call failed (isError true).
statusNo
next_stepsNo
max_per_keyNo
saved_searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well past the annotations by specifying idempotent behaviour (same normalised query returns status "already_saved" and writes nothing), quotas (20 per key, 50 saves per key per UTC day with RATE_LIMITED), required searches:write scope, PII restrictions, redaction and 180-day retention including deletion with the account.

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?

Front-loaded with purpose and alternatives, and nearly every clause carries operational information; the density of quotas, scopes, retention and return keys in one block makes it slightly heavy to scan, but there is no filler sentence.

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?

For a 13-parameter mutation tool it covers what an agent needs: prerequisites, idempotency, limits, privacy handling, lifecycle, and even the returned keys, so nothing material is left to inference despite the output schema already existing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100 percent, so the field meanings are already documented, but the description still adds real constraint on two parameters by forbidding personal data in "name" and "query" and explaining the redaction and retention consequence.

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?

States a specific verb and resource (save a search = query plus filters of pitchspark_search_pitches_v2) and names the retrieval sibling pitchspark_list_saved_searches_v1, so an agent can distinguish it from the search tools without opening a schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use trigger (the investor asks to save or remember a search) and explicit when-not cases with alternatives: not for alerts, since saving delivers nothing, and not for running the search, which is pitchspark_search_pitches_v2.

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