Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

seo_open_graph_generator

Read-onlyIdempotent

Generate Open Graph meta tags with type-specific sub-namespaces and Facebook share-card preview. Input structured fields; output assembled meta HTML and warnings.

Instructions

Open Graph Protocol Meta Tag Generator. Generate an Open Graph (ogp.me) meta-tag block from structured fields, plus type-specific sub-namespaces for article / book / profile / video and music types and a live Facebook share-card preview. Use seo_meta_tag_generator instead when you want a full head block (Twitter Card, canonical, robots, optional WebPage JSON-LD); use this tool when you need only the og tags with vertical sub-properties. Set operation to presets to fetch four worked example payloads. Runs locally on the data you supply: read-only, non-destructive, contacts no external service, and is rate-limited (60 requests/minute for anonymous callers). Returns the assembled meta HTML, a warnings list (length truncation, missing og image or og url, non-absolute URLs, unknown og type, bad BCP 47 locale), and a preview record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNogenerate assembles the meta block (title and description required); presets returns four example input records and ignores all other fields.generate
titleNoog:title text. Required for generate. Warns when over 60 chars (Facebook truncates the share card).
descriptionNoog:description text. Required for generate. Warns when over 65 chars (Facebook truncates the share card).
imageNoog:image URL. Should be an absolute https URL at 1200x630 (1.91 to 1); relative URLs raise a warning.
urlNoog:url canonical permanent URL of the page. Should be absolute with scheme; non-absolute raises a warning.
siteNameNoog:site_name brand label. Optional; emitted only when non-empty.
localeNoog:locale IETF BCP 47 tag such as en_US or pt-BR. Underscore or hyphen accepted; off-pattern values raise a warning.
typeNoog:type. Unknown values still emit but warn and behave as website. Selects which vertical sub-namespace is read.website
articleNoRead only when type is article. Fields author, publishedTime, modifiedTime, expirationTime, section (strings) and tag (string array).
bookNoRead only when type is book. Fields author, isbn, releaseDate (strings) and tag (string array).
profileNoRead only when type is profile. Fields firstName, lastName, username, gender (strings).
videoNoRead only when type starts with video. Fields actor, director, writer, duration, releaseDate, series (strings) and tag (string array).
musicNoRead only when type starts with music. Fields duration, album, musician (strings).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoTrue when the operation completed.
operationNoEcho of the requested operation (generate or presets).
resultNoFor generate: html (the assembled meta-tag block string), warnings (array of advisory strings), and preview (object with title, description, image, siteName, host derived from og url). For presets: a presets array of example input records.
Behavior5/5

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds key behavioral context: runs locally, read-only, non-destructive, contacts no external service, rate-limited (60 req/min). This goes beyond annotations, giving agents clear safety and performance expectations.

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?

Description is relatively long but front-loaded with main purpose and key differentiator. Structured with clear sections (main use, alternative, operation modes, behavioral notes). Every sentence adds value. Could trim some redundancy but still effective.

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 (13 parameters, nested objects, enum types), the description covers all necessary aspects: what it does, when to use, behavioral traits, parameter constraints, and return summary. Output schema exists so return explanation not needed. Complete for an AI agent.

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?

Schema description coverage is 100%, so baseline 3. Description adds value by noting warnings for length truncation, relative URLs, unknown og type, bad locale. Provides context like 'Required for generate' for title/description. Doesn't just repeat schema, adds practical usage details.

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?

Clearly states the tool generates Open Graph Protocol meta tags. Explicitly distinguishes from sibling seo_meta_tag_generator by specifying use case: 'use this tool when you need only the og tags with vertical sub-properties' versus a full head block. Verb+resource is specific.

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?

Provides explicit guidance on when to use vs alternatives: mentions seo_meta_tag_generator for full head block. Also describes operation=presets for fetching example payloads. Covers both main use and auxiliary feature.

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