Hook Detector

list_folders

Your folders, the most recently changed first, each with item_count, up to 4 cover thumbnails and its share link when shared. With hook_id or find_id, each folder also has contains: the item id when it holds that video (any run's copy), else null. Returns {"folders": [...], "count"}. Same as GET /v1/folders. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_folders"
  }
}

Input Schema

Name	Required	Description
`kind`	No	only "short", "long" or "packaging"; leave out for every tab
`api_key`	No
`find_id`	No	say which folders already hold this find's video
`hook_id`	No	say which folders already hold this hook

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Since no annotations exist, the description carries the full weight. It provides important behavioral context such as the defined return structure ({"folders": [...], "count"}) and the data contained within the folder objects (item_count, cover thumbnails, share link).

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

Conciseness3/5

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

The description is dense and front-loaded with features (sorting, metadata, filter results), making it slightly harder to digest than a simple, concise summary. It tries to cram too much operational detail into a single block.

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?

It is highly complete for a listing operation. It covers what is returned, how it is sorted, and the specific impact of the available filters on the output structure, leaving no major functional ambiguity for the agent.

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?

With 75% schema coverage, the baseline is mid-range. The description adds value by explaining the practical semantic outcome of using `hook_id` or `find_id`, specifically how it populates the `contains` field.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the resource being acted upon ('Your folders') and the primary action ('list'). It distinguishes its specific features by detailing the contents and the functionality of filters.

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?

It includes useful usage information like the sorting order ('most recently changed first') and the cost ('Free'). However, it does not explicitly state when to use this tool versus a more specific sibling like 'get_folder'.

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?