Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

seo_schema_org_generator

Read-onlyIdempotent

Generate schema.org JSON-LD structured data markup for 17 supported types. Paste ready-to-use script tags into your page head with validation warnings for missing fields.

Instructions

Schema.org JSON-LD Structured Data Generator. Generate schema.org JSON-LD structured-data markup for any of 17 supported types (Article, BlogPosting, NewsArticle, Product, LocalBusiness, Organization, Person, Event, Recipe, FAQPage, BreadcrumbList, VideoObject, Review, Course, JobPosting, HowTo, SoftwareApplication) from the fields you supply, ready to paste into a page head. Use seo_meta_tag_generator for the broader head meta block (it can embed a single WebPage JSON-LD), seo_open_graph_generator for og: social-share tags, and webdev_json_schema_generator for JSON Schema validation contracts (not schema.org). Send operation schemas first to discover each type required/ recommended/optional field names. Runs locally on the data you provide: read-only, non-destructive, contacts no external service, and is rate-limited (30 requests/minute for anonymous callers). Returns the JSON-LD object, a pretty-printed string, a ready script tag, and validation warnings for any missing required/recommended fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNogenerate builds JSON-LD from type + fields; schemas ignores other inputs and returns the field spec for every supported type.generate
typeNoschema.org type to generate. Required when operation is generate; unknown values are rejected.
fieldsNoFlat record keyed by the chosen type field names (e.g. headline, author, datePublished for Article). Strings, arrays, or nested objects (person with name/url; offer with price/priceCurrency; address; rating; questions; steps; breadcrumbs). Empty values are dropped. Run operation schemas for the per-type field list.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the request succeeded.
operationNoThe operation performed (generate or schemas).
resultNoFor generate: the structured-data payload. For schemas: a schemas array catalog of supported types.
Behavior5/5

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

The description goes beyond annotations by stating the tool is read-only, non-destructive, local, and rate-limited. This adds critical behavioral context not captured in annotations.

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 efficiently structured with front-loaded purpose. Each sentence contributes meaning. Slightly longer than minimal but appropriate for the complexity.

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?

Given the tool's complexity (17 types, two operations, output schema), the description covers all necessary aspects: purpose, usage, behavioral traits, output details, and sibling references. No gaps identified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, the baseline is 3. The description adds value by explaining how to use the 'fields' parameter and referencing operation schemas for field details, slightly exceeding the baseline.

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

Purpose5/5

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

The description clearly states the tool generates schema.org JSON-LD structured data for 17 types. It distinguishes from siblings like seo_meta_tag_generator and seo_open_graph_generator, making the purpose unambiguous.

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

Usage Guidelines5/5

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

Explicitly tells when to use this tool vs alternatives (e.g., 'Use seo_meta_tag_generator for the broader head meta block') and advises to run the 'schemas' operation first. This provides clear usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server