Skip to main content
Glama
Sign In

Teppek

by com.teppek
OverviewDiscussionsAdmin
This connector has been deprecated

Replaced by Teppek.

Duplicate listing. Use the main Teppek connector.

request_image_upload

Get a short-lived upload grant to attach a photo to a listing you're about to publish (any vertical/role). Returns { key, upload_url, upload_token, headers_required }: PUT the raw image bytes to upload_url with those headers, then pass the returned key in create_listing's images array. Images are AI-moderated for content safety before the listing goes live.

Input Schema

NameRequiredDescriptionDefault
file_sizeYesExact file size in bytes, at most 10485760 (10 MB). Example: 2097152 for a 2 MB file.
content_typeYesMIME type of the image file. Example: "image/png".

Output Schema

NameRequiredDescriptionDefault
keyNo
upload_urlNo
upload_tokenNo
headers_requiredNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / content_type / description
      Added value: +"MIME type of the image file. Example: \"image/png\"."
    • changedInput schema / properties / content_type / enum
      Previous value: -[
-  "image/jpeg",
-  "image/png",
-  "image/webp",
-  "image/avif"
-]New value: +[
+  "image/jpeg",
+  "image/png",
+  "image/webp"
+]
    • addedInput schema / properties / file_size / description
      Added value: +"Exact file size in bytes, at most 10485760 (10 MB). Example: 2097152 for a 2 MB file."
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "headers_required": {
+      "additionalProperties": {},
+      "properties": {},
+      "type": "object"
+    },
+    "key": {
+      "type": "string"
+    },
+    "upload_token": {
+      "type": "string"
+    },
+    "upload_url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare the operation is not read-only, not idempotent, and not destructive; the description adds substantive behavior: the grant is short-lived, returns upload credentials, requires a PUT of raw bytes with specified headers, and triggers AI moderation before the listing goes live. There is no contradiction with the annotations.

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 description is front-loaded with purpose, then provides the return shape and upload workflow, then closes with the moderation note. Every sentence carries useful information and there is no redundant restatement.

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 simple two-parameter schema, full schema coverage, annotations, and an output schema, the description supplies everything an agent needs: the grant workflow, how to use the returned fields, where the key goes, and the moderation gate. No critical operational detail is missing for this tool.

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 both content_type and file_size fully documented, including the enum and 10 MB maximum. The description adds workflow context but does not add meaning beyond the schema for either parameter, so the baseline of 3 is appropriate.

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 states a specific verb and resource: get a short-lived upload grant for attaching a photo to a listing about to be published. It also names create_listing as the downstream consumer, which distinguishes this pre-publish upload grant from update_listing_images used for existing listings.

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 clearly states the context: use this when you need to attach an image to a listing you're about to publish, then pass the returned key into create_listing's images array. It does not explicitly mention the update_listing_images alternative or when not to use this tool, so it stops short of full when/when-not guidance.

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

All Teppek toolsInspect
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