Skip to main content
Glama

Niche: Your niche, followed for you

by com.nicheangle
OverviewDiscussionsAdmin

List sessions

niche_list_sessions
Read-only

List your recent scans: id, the niche you described, status and timestamps. Use it to find a session_id you no longer have.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax sessions to return (default 25, max 100).
offsetNoSkip this many sessions before returning, for paging through history. Default 0.
status_filterNoOptional scan status, such as cp1_awaiting_story, cp2_awaiting_angle, complete, or failed.
niche_containsNoOptional case-insensitive substring filter on the niche input, to find sessions on a topic (e.g. 'walnut').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / brand_id
      Removed value: -{
-  "description": "Optional filter to sessions tied to one brand profile slot.",
-  "type": "string"
-}
    • removedInput schema / properties / include_outputs
      Removed value: -{
-  "default": false,
-  "description": "When true, also returns `recent_outputs`: the account's produced posts/images/reels across all sessions, newest first, each with its session_id, cell, a reachable asset_url, and publish state. Use it to locate a past asset (e.g. an image made on a prior run). Default false.",
-  "type": "boolean"
-}
    • changedInput schema / properties / status_filter / description
      Previous value: -"Optional status filter, e.g. 'cp1_awaiting_story', 'cp3_awaiting_review', 'complete', 'failed'. Omit for all."New value: +"Optional scan status, such as cp1_awaiting_story, cp2_awaiting_angle, complete, or failed."
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description usefully adds the shape of the returned list, but says nothing about ordering, pagination behavior beyond the schema, or result size limits.

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?

Two tight sentences, with the returned-field summary front-loaded and the use case immediately after. No filler.

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 compensates by listing the returned fields. All four optional parameters are covered by the schema, so an agent has enough to call it; only ordering/pagination nuances are left implicit.

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 description coverage is 100%, so limit, offset, status_filter and niche_contains are fully documented in the schema. The description adds no filtering or paging semantics beyond that, which meets the baseline for a well-documented schema.

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?

States a specific verb (List) and resource (your recent scans) and enumerates the returned fields: id, niche, status, timestamps. It is clearly distinguishable from mutation siblings like niche_session_cancel, though it does not explicitly name a sibling by contrast.

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?

'Use it to find a session_id you no longer have' gives a concrete trigger condition for calling the tool. It stops short of naming alternatives such as niche_session_state for inspecting one known session, so no exclusions are stated.

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

All Niche: Your niche, followed for you 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