Financial Modeling Prep MCP Server

searchCrowdfundingCampaigns

Read-onlyIdempotent

Search crowdfunding campaigns by company, campaign name, or platform to retrieve detailed activity data for tracking and analysis.

Instructions

Search for crowdfunding campaigns by company name, campaign name, or platform with the FMP Crowdfunding Campaign Search API. Access detailed information to track and analyze crowdfunding activities.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description	Default
`name`	Yes	Company name, campaign name, or platform to search for

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.9.0Nov 6, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

First observedAug 16, 2025

TDQS

B3.1/5.0

Behavior2/5

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

Annotations already cover read-only, idempotent, and open-world behavior. The description adds no further behavioral context, such as pagination limits, result ordering, authentication requirements, or what 'detailed information' actually includes. The phrase 'Access detailed information to track and analyze crowdfunding activities' is too generic to be useful.

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

Conciseness3/5

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

The definition is two sentences, but the second sentence is generic filler ('Access detailed information to track and analyze crowdfunding activities') and the first includes a redundant vendor API name. The core purpose is front-loaded, but the text could be tightened significantly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter search tool with full schema coverage and clear annotations, the description is adequate but minimal. It does not explain what type of records or fields are returned, which would help an agent understand the output given the absence of an output schema.

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% and the single parameter is fully documented in the schema itself. The description repeats the same fields (company name, campaign name, platform) without adding new meaning, syntax, or examples, so the baseline score of 3 is appropriate.

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 ('crowdfunding campaigns'), and lists the searchable dimensions (company name, campaign name, platform). It does not explicitly differentiate itself from sibling tools like getLatestCrowdfundingCampaigns or getCrowdfundingCampaignsByCIK, but the core purpose is clear.

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?

The description implies usage when searching by a specific company name, campaign name, or platform, but offers no explicit guidance on when to choose this tool over alternatives such as getLatestCrowdfundingCampaigns or getCrowdfundingCampaignsByCIK. No exclusions or prerequisites are mentioned.

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

Deploy Server