Social Fetch

Get Facebook profile

facebook_profile_get

Read-only

Get a Facebook profile or Page by URL or username.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	No	Facebook public profile or page URL to look up.
`link`	No	Alias for `url`. Prefer `url`.
`path`	No	Alias for `url`. Prefer `url`.
`trim`	No	Ignored if this tool does not support it.
`limit`	No	Ignored if this tool does not support it.
`offset`	No	Ignored if this tool does not support it.
`context`	Yes	Describe the user's underlying goal in one sentence — not the tool you are calling.
`tweetId`	No	Alias for `url`. Prefer `url`.
`pageSize`	No	Ignored if this tool does not support it.
`tweetUrl`	No	Alias for `url`. Prefer `url`.
`tweet_id`	No	Alias for `url`. Prefer `url`.
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`permalink`	No	Alias for `url`. Prefer `url`.
`tweet_url`	No	Alias for `url`. Prefer `url`.
`maxResults`	No	Ignored if this tool does not support it.
`max_results`	No	Ignored if this tool does not support it.
`conversation_id`	No	Echo 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.
`includeBusinessHours`	No	Optional: include structured business hours in the response when available.

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedSep 21, 2026

addedInput schema / properties / limit

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / link / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / link / type
```
Removed value: -"string"
```

addedInput schema / properties / maxResults

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / max_results

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / offset

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / pageSize

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / path

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Alias for `url`. Prefer `url`."
+}

addedInput schema / properties / permalink / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / permalink / type
```
Removed value: -"string"
```

addedInput schema / properties / trim

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / tweetId / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / tweetId / type
```
Removed value: -"string"
```

addedInput schema / properties / tweetUrl / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / tweetUrl / type
```
Removed value: -"string"
```

addedInput schema / properties / tweet_id / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / tweet_id / type
```
Removed value: -"string"
```

addedInput schema / properties / tweet_url / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / tweet_url / type
```
Removed value: -"string"
```

Changed7 schema fields changedSep 12, 2026

addedInput schema / properties / link

Added value: +{
+  "description": "Alias for `url`. Prefer `url`.",
+  "type": "string"
+}

addedInput schema / properties / permalink

Added value: +{
+  "description": "Alias for `url`. Prefer `url`.",
+  "type": "string"
+}

addedInput schema / properties / tweetId

Added value: +{
+  "description": "Alias for `url`. Prefer `url`.",
+  "type": "string"
+}

addedInput schema / properties / tweetUrl

Added value: +{
+  "description": "Alias for `url`. Prefer `url`.",
+  "type": "string"
+}

addedInput schema / properties / tweet_id

Added value: +{
+  "description": "Alias for `url`. Prefer `url`.",
+  "type": "string"
+}

addedInput schema / properties / tweet_url

Added value: +{
+  "description": "Alias for `url`. Prefer `url`.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "url",
-  "context",
-  "llm_model"
-]New value: +[
+  "context",
+  "llm_model"
+]

Changed5 schema fields changedSep 5, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / context

Added value: +{
+  "description": "Describe the user's underlying goal in one sentence — not the tool you are calling.",
+  "type": "string"
+}

addedInput schema / properties / conversation_id

Added value: +{
+  "description": "Echo 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.",
+  "type": "string"
+}

addedInput schema / properties / llm_model

Added value: +{
+  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "url"
-]New value: +[
+  "url",
+  "context",
+  "llm_model"
+]

Changed1 schema field changedAug 27, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed1 schema field changedJul 29, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedJul 20, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds no additional behavioral context, such as return format, error handling, pagination, or rate limits. It simply restates the action without enriching the agent's understanding beyond 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, direct sentence that is front-loaded with the action and resource. It is efficient and free of filler, though it is brief and omits the nuance of which parameter to use for a username. Still, it is appropriately concise for a simple get operation.

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

Completeness2/5

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

Given the tool's complexity (18 parameters, many aliases and ignored fields), the description is insufficient. It does not clarify that 'url' is the primary parameter, nor that most others are aliases or ignored. It also does not describe what the response contains. The agent would need to inspect the schema thoroughly to avoid misusing the 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?

All 18 parameters have schema descriptions (100% coverage), so the schema already documents each field. The description mentions 'by URL or username' but does not map 'username' to any specific parameter; the schema only exposes 'url' and aliases. No additional meaning beyond the schema is provided, and the 'username' mention could cause confusion.

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 action ('Get') with a clear resource ('Facebook profile or Page') and an explicit input method ('by URL or username'). This clearly distinguishes it from sibling tools like facebook_profile_posts_list or facebook_profile_events_list, which retrieve specific content types rather than the profile itself.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention any exclusions, conditions, or sibling tools. For example, it does not say 'Use this for basic profile info; for posts use facebook_profile_posts_list.' The usage context is only implied by the tool name.

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

All Social Fetch tools Inspect

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.

Get Facebook profile

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources