Skip to main content
Glama

Heista

by co.heista

Community Search (Reddit / X / Substack / LinkedIn)

search_community
Read-only

Community-discourse search via parallel.ai with optional platform filtering. Returns synthesized text excerpts plus direct URLs to real Reddit threads, X posts from named operators, Substack essays, LinkedIn posts, Facebook posts.

Use for: "what are practitioners saying about X", recurring themes in founder voice, multi-platform discourse mapping, verbatim quotes from named individuals.

Per Phase 3.5 empirical A/B (Docs/solutions/architecture-decisions/search-backend-architecture-jun04.md): this tool SOLVES the Reddit/X retrieval gap that perplexity_search fundamentally couldn't fill.

Optional platforms[] to restrict (e.g. ["reddit","x","substack"]). Per social-listening-synthesis §3 sample ≥3 platforms per brief.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query. Phrase as natural-language. Focused on what people are SAYING — practitioner voice, named-operator discourse, community reaction. Not a general fact-check query.
platformsNoLimit search to these platforms. Use ["reddit"] for r/* threads, ["x","twitter"] for X posts, ["substack"] for named essays. Omit to let the search engine choose. Per social-listening-synthesis §3 sample ≥3 platforms per brief — pass at least 3 here for multi-platform discourse mapping.
after_dateNoISO date (YYYY-MM-DD). Restrict to content after this date. Use for recency-sharp community signal mapping.
max_resultsNoMaximum results. Default 10.

TDQS

A4.7/5.0
Behavior4/5

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

Annotations indicate readOnly (true) and openWorld (true), which the description aligns with by describing a read-only search that returns real content. The description adds behavioral context: the search is via parallel.ai, returns synthesized excerpts plus direct URLs, and solves a specific retrieval gap. No contradictions.

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 front-loaded with the core function, followed by use cases and parameter guidance. However, it includes a somewhat verbose reference to an internal document ('Phase 3.5 empirical A/B'), which could be shortened without losing meaning. Overall, it is efficient and well-organized.

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 no output schema, the description compensates by detailing return content (synthesized text plus URLs). It explains the tool's purpose, differentiation, and parameter options thoroughly. The context of multi-platform discourse mapping and the reference to social-listening-synthesis provide sufficient completeness for an agent to select and use 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?

Schema coverage is 100%, but the description adds significant meaning beyond the schema descriptions. For 'query', it clarifies it should be natural-language and focused on practitioner voice. For 'platforms', it provides concrete examples and a recommendation (≥3 platforms). It also reinforces the usage of 'after_date' and 'max_results'. This provides actionable guidance.

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 it performs 'community-discourse search' across multiple platforms, returning synthesized text excerpts and URLs. It explicitly distinguishes itself from perplexity_search, naming the gap it fills (Reddit/X retrieval). The verb 'search' combined with the resource 'community' is specific and informative.

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?

The description provides explicit use cases ('Use for:...'), including specific examples like 'what are practitioners saying about X' and 'verbatim quotes from named individuals'. It compares the tool to perplexity_search, highlighting its unique value. It also gives platform selection guidance, referencing an internal document for best practices.

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

All Heista 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.7/5.0
Disambiguation4/5

Despite the high tool count, most tools have distinct purposes with thorough descriptions that specify when to use each. Some overlap exists among creative direction tools (call_creative_worlds vs chat_with_creative_worlds), but the descriptions clarify usage patterns.

Naming Consistency3/5

Naming conventions are inconsistent overall: some follow verb_noun (create_powersource_url, decode_ad), others use noun_verb or compound names (adformula_intelligence, fleet_analytics_overview). However, subgroups like dispatch_* and list_*_presets maintain internal consistency.

Tool Count2/5

112 tools is far beyond the typical 3-15 range for well-scoped servers. While the server covers a broad domain, the sheer number likely overwhelms agents and suggests insufficient consolidation of related operations.

Completeness4/5

The tool set covers core creative intelligence workflows: brand analysis, ad decoding, script generation, creative direction, and research. Minor gaps exist (e.g., no social media publishing tools), but the main use cases are well-supported.

Resources