API Ninjas

getRandomImage

Read-only

Returns a random royalty-free image, optionally constrained by category, width and height. Useful for placeholder or sample imagery.

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

Input Schema

Name	Required	Description
`width`	No	Width of the image to generate. Must be between 1 and 5000. Default value is 640. Premium only.
`height`	No	Height of the image to generate. Must be between 1 and 5000. Default value is 480. Premium only.
`category`	No	Image category. If set, must be one of the following: nature, city, technology, food, still_life, abstract, wildlife. Premium only.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description usefully adds that images are royalty-free and that constraints are optional, but omits notable traits such as the premium-only gate on width/height/category or the return format.

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 core action front-loaded and no filler. Every clause carries information.

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?

For a simple zero-required-param read tool this is nearly complete. With no output schema, the description could have stated the returned artifact (URL vs. binary), which is the one remaining gap.

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 the enum values and the 1-5000 bounds are fully documented in the schema. The description only restates the parameter names as optional constraints, adding no meaning beyond the 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 (returns) and resource (a random royalty-free image) plus the optional constraints. It is unambiguous and no sibling produces random imagery, so there is little to distinguish it from, but it stops short of naming any related tool.

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?

"Useful for placeholder or sample imagery" gives an implied usage context. There is no explicit when-to-use / when-not guidance and no named alternative, so it sits at minimum-viable rather than a full routing statement.

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

All API Ninjas 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?