Skip to main content
Glama

Honeyfield Marketing MCP

Business Profile: Upload media

gbp_upload_media

Foto anhand einer Quell-URL hochladen. Achtung: wird öffentlich sichtbar im Business-Profil angezeigt — nur nach Bestätigung hochladen. category: COVER | PROFILE | LOGO | EXTERIOR | INTERIOR | PRODUCT | AT_WORK | FOOD_AND_DRINK | MENU | COMMON_AREA | ROOMS | TEAMS | ADDITIONAL. workspace: Slug des Kunden-Workspace (optional bei nur einem Workspace).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "source_url": "<source_url>"
    },
    "name": "gbp_upload_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoADDITIONAL
workspaceNo
source_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already mark this as a non-read-only, open-world, non-destructive operation. The description adds important behavioral context beyond that by warning that the uploaded image becomes publicly visible and should only be uploaded after confirmation.

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?

The purpose is front-loaded in the first sentence, followed by the essential public-visibility warning and the non-obvious parameter notes. The category list is lengthy but necessary given that the schema does not enumerate those values.

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 public media-upload mutation, the description covers the key visibility and confirmation concerns plus the parameter semantics that the schema lacks. It does not mention authentication, rate limits, or supported media constraints, but the output schema handles return-value information.

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 0%, so the description must carry parameter meaning; it does by listing allowed category values, noting workspace is optional when there is only one workspace, and identifying source_url as the photo source URL. It still does not clarify source URL accessibility requirements or file constraints.

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 states a specific verb and resource: upload a photo from a source URL. The tool name and description make its upload role clear, but it does not explicitly differentiate itself from siblings such as gbp_list_media or gbp_delete_media.

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?

It gives a clear usage condition: the media becomes publicly visible in the Business Profile, so it should only be uploaded after confirmation. It does not name alternatives or mention when to inspect existing media first.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources