Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Behance tag downloadable projects

behance_tag_get
Read-onlyIdempotent

Fetch a Behance tag and the projects under it that provide downloadable source files, using a tag slug or title.

Instructions

Get a Behance tag and the projects carrying downloadable source files under it. Requires tag.

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": {
      "tag": "<tag>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "behance_tag_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagYesRequired. Tag slug or title, e.g. `2d-animation` or `UI/UX`. A title with spaces uses its hyphenated slug, e.g. `graphic-design`. In a URL path, encode the slash in `UI/UX` as `%2F`; send the tag itself unchanged.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds one genuine behavioral fact beyond that - results are restricted to projects with downloadable files - but says nothing about pagination, result volume, or whether an unknown tag errors or returns empty.

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?

Two short sentences, front-loaded with the purpose and the downloadable-files scope before the requirement. The trailing 'Requires `tag`' is redundant with the schema and could be dropped, but the text is otherwise waste-free.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only lookup with no output schema, the description gives a reasonable sketch of what comes back (the tag plus its downloadable projects). It omits pagination/result-size behavior and the empty-result case, which an agent needs to plan calls.

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%, so the schema already documents tag slug formatting, the slash-encoding case, and the context/llm_model/conversation_id protocol. The description adds nothing beyond 'Requires `tag`', which is the baseline for fully covered schemas.

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 ('Get a Behance tag and the projects...') and adds a meaningful scope qualifier: only projects carrying downloadable source files. This distinguishes it from a generic tag fetch or a profile project list, though it never names the sibling it competes with.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative, despite siblings like behance_tags_list and behance_profile_projects_list existing. 'Requires `tag`' merely restates the schema's required array and adds no routing information.

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