Skip to main content
Glama
Sign In

DialogBrain

by com.dialogbrain.api
OverviewDiscussionsAdmin

group_search

Search for public groups or channels by topic on Telegram (or other channels). Returns matching groups with title, member count, and whether messages can be previewed.

Finds public groups/channels by topic — NOT individual people. To find or add a specific person by @username, use contacts.discover / contacts.find instead.

When to use:

  • Finding groups related to a topic or niche

  • Building a list of groups for outreach or monitoring

After searching, use group.scan to evaluate quality before joining.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return (1-50, default 20)
channelYesChannel to search on (e.g. 'telegram')
keywordsYesSearch keywords or phrase (e.g. 'crypto trading signals'). A list of keywords is also accepted and joined with spaces.
account_idNoWhich of the workspace's accounts on this channel acts (from channels.list). OMIT to use the workspace's default account.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / account_id
      Added value: +{
+  "description": "Which of the workspace's accounts on this channel acts (from channels.list). OMIT to use the workspace's default account.",
+  "type": "integer"
+}
  2. Added
  3. Removed
  4. Changed1 schema field changed
    • changedInput schema / properties / keywords / description
      Previous value: -"Search keywords or phrase (e.g. 'crypto trading signals')"New value: +"Search keywords or phrase (e.g. 'crypto trading signals'). A list of keywords is also accepted and joined with spaces."
  5. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, openWorldHint=false, idempotentHint=false, destructiveHint=false, which does not fully tell the agent what the call does to the outside world. The description compensates by stating what the response contains (title, member count, message-preview availability) and by pointing to group.scan as the quality gate before joining. It does not explain why this is not read-only or whether results are cached, so it stops short of a 5.

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?

Front-loaded with the core action and scope in the first sentence, then exclusion, then bullets. Slightly redundant between "by topic" and "groups related to a topic or niche," but nothing is wasted at the level of the whole text.

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 no output schema, the description correctly takes on the burden of describing return fields, and it covers the cross-channel scope and the downstream workflow. It leaves unexplained only edge behavior (empty results, per-channel limits), which is minor for a search tool.

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 coverage is 100%, so every parameter including limit bounds, account_id, and in_workspace is already documented structurally; the baseline of 3 applies. The description adds only a topical framing for keywords ("by topic") and no syntax, formatting, or default-behavior detail beyond the schema.

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?

States a specific verb and resource ("Search for public groups or channels by topic on Telegram") and immediately distinguishes the target from people: "NOT individual people." It even names the sibling tools (contacts.discover / contacts.find) that handle the person case, so the agent can route without opening a schema.

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?

Explicit "When to use" bullets cover the two intended scenarios (topic discovery, list building), an explicit when-not with a named alternative, and a follow-up step ("use group.scan to evaluate quality before joining"). That is the full when/how/next pattern.

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

All DialogBrain toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources