Your Echo — The A2A-native PR & Outreach Agent

find_linkedin_groups

Discover active LinkedIn Groups and professional associations for any niche. Review each group and join manually to build your network.

Instructions

Discover the most active LinkedIn Groups and professional associations for a niche. Assist-only — you review + join manually (LinkedIn TOS forbids automation). Public demo.

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": {
      "niche": "<niche>"
    },
    "name": "find_linkedin_groups"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`niche`	Yes
`region`	No
`seniority`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.2Jul 9, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the burden. It discloses the assist-only requirement and TOS restriction, which is useful. However, it lacks details on rate limits, authentication needs, or what 'most active' means. The 'Public demo' note adds ambiguity about reliability.

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?

The description is two sentences, front-loaded with the purpose, and each sentence serves a distinct function (purpose and behavioral note). No unnecessary words.

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

Completeness2/5

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

Given 4 parameters, no descriptions in schema, and no output schema, the description is insufficient. It does not explain what the tool returns, how parameters like 'limit' affect results, or what 'most active' means. The completeness is low for a tool with this complexity.

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

Parameters2/5

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

Schema coverage is 0% meaning no parameter descriptions in the schema. The description only implies the 'niche' parameter by saying 'for a niche'. It does not explain 'limit', 'region', or 'seniority', so it adds almost no value beyond the schema for 3 of 4 parameters.

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 the action 'discover', the resource 'LinkedIn Groups and professional associations', and the scope 'most active... for a niche'. It distinguishes from sibling tools like discover_communities and find_and_pitch by specifying the exact resource and the assist-only nature.

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 explicitly says 'Assist-only — you review + join manually (LinkedIn TOS forbids automation)', which provides clear context for when to use this tool (research/discovery) and implies not to use it for automated actions. However, it does not explicitly compare to alternatives or state when not to use.

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

Deploy Server