Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

image-urlPlaceholder

Generate random placeholder image URLs with custom text, dimensions, format, and colors for mockups or UI testing. Deprecated due to poor uptime; use Faker image URL or data URI instead.

Instructions

Generates a random image url provided via https://via.placeholder.com/. (Deprecated: The service has bad uptime. Use faker.image.url() or faker.image.dataUri() instead.)

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": "image-urlPlaceholder"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoThe text to display on the image.
widthNoThe width of the image.
formatNoThe format of the image.
heightNoThe height of the image.
textColorNoThe text color of the image.
backgroundColorNoThe background color of the image.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden; it usefully discloses the external dependency and the reliability problem ("bad uptime"). It says nothing about randomness/determinism, rate limits, or failures, and only weakly signals that the result is a single URL string.

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 sentences, front-loaded with what it does, then the deprecation warning and alternatives. No filler or restated schema content.

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?

No annotations and no output schema, but the description implicitly identifies the return (an image URL) and flags the external service risk, which is the main thing an agent needs for this simple generator. A note on determinism or return-string format would close the 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% with 6 fully documented params including an enum for format, so the schema does the heavy lifting. The description adds no meaning about text, colors, dimensions, or defaults, so 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?

States a specific verb and resource ("Generates a random image url") plus the backing service (via.placeholder.com), so the agent knows exactly what it produces. It does not differentiate from the closest siblings (image-urlLoremFlickr, image-urlPicsumPhotos), and the alternatives it names (faker.image.url / faker.image.dataUri) are library calls rather than sibling tools, so an agent cannot route to them within this catalog.

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?

Gives explicit when-NOT guidance via the deprecation note and names two preferred replacements, which is more than most definitions supply. However, the suggested replacements are not resolvable sibling tools here, so the routing advice is only partially actionable.

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

Deploy Server

Other Tools