TrendIdea

generate_content

Idempotent

Generate ready-to-use marketing and business content for an idea: blog posts, social media, ad copy, press releases, elevator pitches and 12 more types. Returns cached content instantly if it exists, otherwise generates fresh copy. Spends credits only when generating new content. Not read-only; pass an ideaId you own and a contentType.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ideaId`	Yes	The idea ID
`language`	No	Content language	en
`contentType`	Yes	Content type: blog_post, social_linkedin, social_twitter, social_instagram, ad_copy_google, ad_copy_meta, press_release, elevator_pitch, email_cold, email_newsletter, landing_copy, investor_update, product_hunt_launch, onboarding_sequence, faq_page, case_study, partnership_pitch

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	The tool result rendered as human and AI readable text or markdown.

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations, the description discloses caching behavior, credit spending, and ownership requirement. It aligns with idempotentHint (cached content) and readOnlyHint=false, adding valuable operational details without contradicting any annotation.

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

Conciseness5/5

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

Four tightly packed sentences, each contributing unique information: purpose, caching, cost, and usage requirement. No filler or repetition of schema details, and the primary action is stated first.

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 3-parameter tool with full schema coverage, an output schema, and rich annotations, the description covers purpose, behavior, cost, and prerequisites. It gives the agent everything it needs to decide to invoke and execute correctly, and the content type list in the schema covers the remaining specifics.

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%, so each parameter is already documented. The description adds the crucial constraint that ideaId must be owned, and reinforces the required contentType. This goes beyond the schema's basic 'The idea ID', providing meaningful usage context.

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 opens with a clear verb-resource pairing ('Generate ready-to-use marketing and business content') and enumerates specific content types, distinguishing it from the get_* read tools. While generate_b2b_pitch is a possible sibling, the description's scope is broader and unambiguous.

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 gives clear context for use (for an idea, with an owned ideaId and a contentType) and notes it's not read-only, but does not explicitly name alternatives or exclusions. The contextual info is enough to know when to reach for this tool, though it stops short of comparing against specific siblings like generate_b2b_pitch.

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

All TrendIdea tools Inspect

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

A4.1/5.0

Disambiguation5/5

Each tool targets a distinct function or data aspect, from idea CRUD to simulations, content generation, and team management. Despite the large number, descriptions clearly differentiate purposes, e.g., 'get_idea_summary' vs. 'get_idea_agents' vs. 'get_idea_evolution'. No two tools appear to do the same thing.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case (e.g., 'create_idea', 'get_competitive_density', 'toggle_favorite'). No mixing of conventions like camelCase or abbreviations. The pattern is uniform and predictable.

Tool Count2/5

63 tools is far beyond the typical well-scoped range of 3-15. While the platform's broad scope (idea validation, B2B, team, simulations) justifies many, the sheer volume can overwhelm an agent. A more curated subset or grouping would improve coherence.

Completeness5/5

The tool set covers the full startup idea lifecycle: creation, validation, retrieval of various analyses, updates, deletion, sharing, simulations, B2B lead generation, team collaboration, and market intelligence. No obvious gaps exist for the stated domain.

Resources

Need Help?