Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

getScreenshotList

Retrieve all screenshot jobs with pagination to review, manage, and track TestingBot cloud screenshot runs by limit and offset.

Instructions

Get a list of all screenshot jobs with pagination.

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": "getScreenshotList"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of screenshot jobs to retrieve (default: 10, max: 100)
offsetNoOffset for pagination (default: 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description has to carry the behavioral detail. It discloses that results are a full list ('all') and that pagination applies, which is meaningful context for a read operation. It says nothing about ordering, job status fields, or whether results are scoped to a user or project.

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 description is a single sentence with no filler and puts the resource and scope first. It is efficient, though its brevity leaves it slightly under-informative rather than padded.

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

Completeness3/5

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

For a simple two-parameter list tool with no output schema, the description minimally suffices. It does not explain what a screenshot job record holds or how results are ordered, which the agent cannot infer from the schema alone.

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%: the schema fully documents limit (default 10, max 100) and offset (default 0). The description only names 'pagination' and adds no meaning beyond the schema, so the baseline 3 applies.

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?

The description gives a specific verb and resource: 'Get a list of all screenshot jobs'. Adding 'with pagination' scopes it further. It implicitly differs from creation siblings like takeScreenshot/tb_screenshot, but it never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this instead of takeScreenshot or tb_screenshot, and no prerequisites or exclusions. The agent must guess whether 'screenshot jobs' are created by those siblings.

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