Skip to main content
Glama

Seedrs / Republic Europe campaigns search

run_seedrs_campaigns_search
Read-onlyIdempotent

Search the live Republic Europe (Seedrs) campaigns by campaign-name word and sector, impact tag, business type, tax relief and pitch type filters: raised and target amounts, valuation, investors, type, status and link. 1 point per returned record.

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": "run_seedrs_campaigns_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort by. Options: trending_desc = Trending (default), trending_asc = Trending (least first), most_recent_desc = Most recent, most_recent_asc = Oldest, percentage_raised_desc = Most raised (%), percentage_raised_asc = Least raised (%), closing_date_asc = Closing soonest, closing_date_desc = Closing latest, business_name_asc = Name A-Z, business_name_desc = Name Z-A, valuation_desc = Valuation (high first), valuation_asc = Valuation (low first), investment_sought_desc = Target (high first), investment_sought_asc = Target (low first), investors_count_desc = Investors (most first), investors_count_asc = Investors (least first)
tagsNoImpact
typesNoPitch type
searchNoCampaign name word. e.g. skytree
sectorsNoSectors
max_itemsNoMax items (up to 250) Default: 25.
trending_inNoTrending in (country code). e.g. GB
business_typesNoBusiness type
include_preregNoInclude pre-registration pages
tax_eligibilitiesNoTax relief

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is low. The description adds genuinely useful non-annotation context: the '1 point per returned record' cost model and the fact that results are 'live' campaigns.

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?

A single front-loaded sentence that leads with the action and resource, then the filters, then the returned fields. It is dense but every clause carries usable information; only the returned-field list could be viewed as slightly over-stuffed.

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?

With 10 all-optional parameters and no output schema, the description usefully compensates by enumerating the returned fields (raised/target amounts, valuation, investors, type, status, link), so an agent knows what it gets back. It is largely complete, missing only sort/paging behavior and credit-cost edge cases.

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 description coverage is 100%, with each parameter and enum option documented inline, so the schema does the heavy lifting. The description names the filter categories (sector, impact tag, business type, tax relief, pitch type) but adds no syntax, format, or combinatorial detail beyond the schema, matching the baseline 3.

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 verb (Search) and resource (live Republic Europe / Seedrs campaigns), and enumerates the filterable dimensions and the fields returned. It implicitly separates itself from run_seedrs_campaigns (single lookup) and run_seedrs_businesses, though it does not name them, so it stops short of full sibling differentiation.

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

Usage Guidelines3/5

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

Usage is implied by 'Search the live ... campaigns by ... filters', giving an agent enough to know it is a discovery/search tool. However, there is no explicit when-to-use vs when-not guidance and no mention of alternatives such as run_seedrs_campaigns for a known campaign.

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.