Hook Detector

get_channel

A channel page: subscribers and totals, every recent long upload scored against the channel itself (outliers at 2x its median and over), and its momentum. Free. Same as GET /v1/channels/{ref}.

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": {
      "ref": "<ref>"
    },
    "name": "get_channel"
  }
}

Input Schema

Name	Required	Description
`ref`	Yes	a UC id, @handle or channel address
`fresh`	No
`api_key`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A3.9/5.0

Behavior4/5

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

The description adds crucial behavioral details beyond the structured fields, explicitly stating the data is 'Free' (cost) and describing the exact logic used for 'outliers' (2x its median). These are important behavioral constraints.

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 definition is dense, packing function, key metrics, operational logic, cost, and the HTTP equivalent into a single impactful statement. While information-rich, it maintains good structure.

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?

The description is very complete regarding the *content* of the result, explaining exactly what metrics are provided (outliers, momentum, etc.). Given that the output schema exists, defining the internal logic of the data is highly valuable.

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?

The schema coverage is low (33%), so the description is needed. It clarifies that 'ref' can be a UC id, @handle, or channel address, which is helpful semantic clarification. However, it adds little context to the optional `fresh` or `api_key` 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 and specifically defines the tool's function as retrieving a 'channel page' containing specific metrics like subscribers, totals, and momentum. It differentiates itself by specifying the sophisticated scoring mechanism (outliers at 2x median).

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 usage is implied by the description's nature (fetching detailed data for a known channel). However, it offers no explicit advice on when to choose this tool over alternatives like `search_channels` or `channel_outliers`.

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

All Hook Detector tools Inspect

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

Need Help?